Ok, sorry, i misunderstood the problem. I thought it was trying to
deploy a servicemix xml
config file.
Feel free to provide a patch so that we can fix the problem. :)
Guillaume
Nicolas Biri wrote:
I've checked svn head and the problem seems to be still present in the
Jboss-deployer...
I've tried to deploy my SA using the deployment bean with the jmx console
of Jboss and it works. The problem is that one can not auto-deploy a SA or
a shared library in JBoss.
I'm currently looking at a solution to this problem. I guess that we can
use the Descriptor to check the kind of archive we have to handle.
Regards,
Guillaume Nodet wrote on 01/12/2005 15:19:19:
Did you check svn head, or 2.0.2 sources ?
I think this has been updated in svn head.
Cheers,
Guillaume Nodet
Nicolas Biri wrote:
I have some news about this problem... I have took a look at the source
of
the JBI deployer for JBoss and I think I've seen the problem : it seems
that all archive with a jbi.xml file placed in the deploy directory of
Jboss is expected to be a component and is deployed as a component.
Consequently, you can not deploy SA and shared libraries in JBoss.
Should I submit a bug report ?
