users@jersey.java.net

Re: [Jersey] Classloader Issues

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Mon, 14 Dec 2009 15:00:18 +0100

On Dec 14, 2009, at 2:52 PM, Cemo Koc wrote:

>
> 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.
>

Yes, and i found that out the hard way :-)


> 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?
>

Yes.


>
> 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.
>

At deployment time there will be a log entry that states 1.1.5-ea-
SNAPSHOT is being utilized for the application.

Paul.