Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.1
-
servicemix-assembly, servicemix-audit, servicemix-bpe, servicemix-common, servicemix-components, servicemix-core, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-soap, servicemix-wsn2005
-
None
-
JBoss 4.0.5 GA
Description
Right now there are no dependencies set on the servicemix components to ensure that they are loaded after the servicemix deployer. This can cause bugs when the component are deployed before the servicemix deployer, and thus are not handled by servicemix (and therefore not available).
The fix for this is do include a dependence in the META-INF/jboss-service.xml of the component .zip file. here is the content of the file :
---------
<?xml version="1.0" encoding="UTF-8"?>
<server>
<depends>org.servicemix:service=Deployer</depends>
</server>
---------
PS : The servicemix-http component already has a jboss-web.xml see issue (SM-584) file this should be deleted and the content of the new jboss-service.xml file should now be :
---------
<server>
<class-loading>
<loader-repository>
org.apache.commons.httpclient:loader=commons-httpclient-3.0.jar
</loader-repository>
</class-loading>
<depends>org.servicemix:service=Deployer</depends>
</server>
-----------
Eric,