Hi Paul,
I did not understand some of the points. Let me to clear them.
1) Is this comment totally true? If it is true are there any other packages
like these?
The webapp classloader ignores the delegate flag for a number of packages,
including any packages starting with javax.* and
org.apache.taglibs.standard.*, and will unconditionally delegate resolution
of any symbols in these packages to the parent classloader.
2) I am assuming that this comment is totally true and so:
Using 1.1.5-ea-SNAPSHOT can not cause problem because all packages delegated
to container are starting with com.sun.* and packages which are not
delegated to container such javax.ws.* can not cause a problem because of no
changes in JAX-WS 1.1 spec?
3 ) Despite of having 1.1.4.1 logs in my log file, how can I be sure that my
application is using 1.1.5-ea-SNAPHOT without removing jersey 1.1.4.1 from
installation folder.
By the way I decided clear everything related to Jersey from my application.
But I just want to make clear to understand better our situation.
Thank for your explanations Paul.
Cem
--
View this message in context: http://n2.nabble.com/Classloader-Issues-tp4163936p4164179.html
Sent from the Jersey mailing list archive at Nabble.com.