Mailing-List: contact dev-help@servicemix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@servicemix.apache.org
Date: Wed, 2 Feb 2011 05:57:29 +0000 (UTC)
From: "Kari J. Niemi (JIRA)" <jira@apache.org>
To: dev@servicemix.apache.org
Message-ID: 
 <750537665.4488.1296626249350.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <29048392.23011291119734294.JavaMail.jira@thor>
Subject: [jira] Commented: (SM-2016) Wait for Shared libraries referred in
 classpath tag of xbean.xml to be deployed.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989525#comment-12989525 ] 

Kari J. Niemi commented on SM-2016:
-----------------------------------

I think this page could "warn" about using the classpath entries in xbean.xml:
http://servicemix.apache.org/classloaders.html

Something like:
-------------
Please notice that using the classpath entries in xbean.xml has some "issues", because a dependency between Service Assembly and JBI Shared Library is not really known by JBI specificationss. Currently the servicemix does not consider this dependency in hotdeployment, so you have to consider these workarounds:
   -if you update the library in hotdeploy folder, the service assembly won't properly pick up the changes. You have to also restart the Service Assembly as well.
   -set a "fake" dependency chain SA-BC-SL. This way, updating the SL will make the BC "reloaded", which will make the SA "reloaded". Also, this will guarantee that in smx startup the SL is loaded before the SA . This is especially important if you removed the data folder, otherwise the SA might be started first and it will most probably fail in classpath problems.
--------------

> Wait for Shared libraries referred in classpath tag of xbean.xml to be deployed.
> --------------------------------------------------------------------------------
>
>                 Key: SM-2016
>                 URL: https://issues.apache.org/jira/browse/SM-2016
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-assembly
>    Affects Versions: 3.3.2
>         Environment: RHEL
>            Reporter: Sandeep T H
>
> Some of our SAs contain SUs which refer to some shared libraries.
> Eg:
> In our cxf-se su:
> <beans xmlns:cxfse="http://servicemix.apache.org/cxfse/1.0" >
> <classpath>
>   <library>common-shareLib</library>
> But sometimes this SA/SU fails to deploy with the errors:
>  java.lang.IllegalStateException  No such shared library common-sharedLib.
> Maybe this is because the SA/SU is deployed before the shared library is deployed. As we've seen if the shared lib is deployed first this problem is not seen.
> We've also tried adding this shared lib as a dependency in cxf-se su pom. But it does not help.
> It is not specific to cxf-se it is seen for other component su's too
> What is the recommended way here?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira