users@jersey.java.net

Re: [Jersey] Classloader Issues

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Tue, 15 Dec 2009 13:06:47 +0100

On Dec 15, 2009, at 1:04 PM, Cemo Koc wrote:

>
> Hi Paul,
>
> As you stated, when I removed delegation flag from descriptor and
> replaced
> necessary bundles I could get rid off that exception. However at my
> log for
> *each request* I could see these:
>
> [#|2009-12-15T13:42:28.592+0200|INFO|glassfishv3.0|
> com.sun.jersey.api.client.Client|_ThreadID=33;_ThreadName=Thread-1;|
> Adding
> the following classes declared in META-INF/services/jersey-client-
> components
> to the client configuration:
> class com.sun.jersey.multipart.impl.MultiPartConfigProvider
> class com.sun.jersey.multipart.impl.MultiPartReader
> class com.sun.jersey.multipart.impl.MultiPartWriter|#]
>
> I have checked my application which has only
> jersey-spring-1.1.5-ea-SNAPSHOT.jar about Jersey... Is this an
> expected
> behaviour?
>

Yes, because jersey-multipart is also distributed with GF so support
automatically gets included with the application.

Paul.