Library Conflict jboss-aop.jar <> jbossall-client.jar (Aspec

[dermas]

Since this has happened more than one time, I guess there should be a solution for the problem:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146554
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146001

The jbossall-client.jar is needed if I like to run my EJBs on the jboss application server. But since jboss as uses aop for his own purposes the jbossall-client.jar has its own version of the AspectManager included.
The result is that you have two different AspectManager versions in your classpath. So it depends on your classpath order if the right AspectManager is used.
In my opionion that is not a desired situation which should be fixed somehow.

[stalep]

yes, atm it is too confusing how the packaged jars are working and how it should work with jboss as. expect some more information or changes soon :)

[kabirkhan]

For AOP 2.0 we need to modify the AS 4 install script to replace the aop client jar, and to patch jbossall-client.jar to use the latest aop client.

[dermas]

Are there any updates on this topic?

[flavia.rainone]

Yes, there are. :)

We have added install scripts to JBoss AOP that solve those conflicts, updates jars, etc. If you give it a try and still find any related errors, let me know.