[ https://issues.apache.org/activemq/browse/SM-452?page=all ]
Guillaume Nodet resolved SM-452:
--------------------------------
Fix Version: 3.0-M2
Resolution: Fixed
Assign To: Guillaume Nodet
I have removed servicemix-components from the lwcontainer, so that one will
need to :
* deploy it in the SU (and put dependencies along)
* put it in the lib/optional folder with the needed dependencies
It seems there is still one problem with activemq-core which is in the
container classloader, but may miss
some dependencies (for example using org.apache.activemq.pool.*).
I think i will improve xbean to support child first class loading delegation
along with exclusions, and it should
be better.
> Classpath issues with lwcontainer
> ---------------------------------
>
> Key: SM-452
> URL: https://issues.apache.org/activemq/browse/SM-452
> Project: ServiceMix
> Type: Bug
> Components: servicemix-lwcontainer
> Versions: 3.0
> Environment: Java 5
> Reporter: Doug Fischer
> Assignee: Guillaume Nodet
> Fix For: 3.0-M2
>
>
> The problem is that the smack jars are loaded from the classloader which
> contains the jabber component, which is the lwconatiner classloader, and not
> from the SU classloader.
> It seems this is a design problem of the lwcontainer.
> I will remove the servicemix-components jar from the lwcontainer, thus you
> will
> have to deploy it inside your service unit, but the problem should be fixed.
> In the mean time, you should be able to copy/paste the jabber component,
> rename it, and bundle it inside your SU with the jar dependencies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
