AFAIK there is no classloader documentation. Your best chance is this list.
You can add jars to lib directory of the mar, it should behave same as
service libs
I belive it should pick up service/lib jars first and then pick up the
jars on WEB-INF/lib. If that is not the case we should be able to
making the core class loader parent of service class loader within
deployment. This could be big change, so if you do not get a good
answer soon, file a bug at Jira.
However if the class you change (u r utility jar) is Axis2 core class,
things might be complex.
Thanks
Srinath
On 1/2/07, Christian Villoslada <[EMAIL PROTECTED]> wrote:
Hello,
I'm looking for documentation concerning the classpath hierarchy for axis2.
My specific configuration has 1 axis2 instance with multiple services
and modules that reuse many of the same utility jars. I would like to
rollout a change to a utility jar and affect one of the services
without affecting all of them.
I seem to run into trouble when a module and a service requires one of
these utility jars. Since any jar placed in {axis2-dir}/WEB-INF/lib
seems to be picked up first by any service instead of a jar in that
service's aar.
Is there a way to put the modify the classpath a service so that it
looks in it's own aar file's lib directory first?
Or is there a better way to go about jar versioning among services and modules?
Also is there a way to include jars in a mar file?
I've searched for documentation concerning this but have not been successful.
Thank you,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
============================
Srinath Perera:
Indiana University, Bloomington
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
