Hi Cemo,
If you take a fresh install of GF v3 and copy the jersey-gf-bundle-
{version}.jar i linked to glassfish/modules/jersey-gf-bundle.jar you
should be able to deploy a Jersey app, the the same version as
{version}, *without* requiring Jersey jars in the war or class loader
delegation set to false. you should not get any exceptions in this case.
The exceptions are only produced when Jersey jars are included in the
war and class loader delegation is set to false. It is hard to get rid
of these exceptions because of the way META-INF/services and class
loading works.
What we really really need is the ability to continuously push
SNAPSHOT versions of Jersey to a publicly accessible GlassFish update
center.
Paul.
On Dec 15, 2009, at 9:51 AM, Cemo Koc wrote:
>
> Hi Paul,
>
> Sorry for my mistake... Now I replaced and renamed yours with bundled
> jersey. And also I have changed jersey-gf-statsproviders.
>
> Now In my logs I can see The MultiPartConfig related exceptions and
> one
> GlassfishMonitoringServiceProvider same as before.
>
> By the way my application is using "delegate=false" flag.
>
> What can I do get rid off especially from first kind of exceptions
> which I
> have a dozen in my log. :)
>
> Thank you so much
>
> Cemo
> --
> View this message in context: http://n2.nabble.com/Classloader-Issues-tp4163936p4168893.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>