dev@glassfish.java.net

Re: lifecycle module classloading delegation

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Tue, 25 Jul 2006 18:23:43 +0200

i think this solution should work for me...
as now i do have 2.0.1 for my lifecycle module, and if deployed WS will
need 2.0 version - will use descriptor's "delegate" feature.

thanks.

WBR,
Alexey.

Kedar Mhaswade wrote:
> Right, that will make his update less painful.
>
> But that will also make app server use the updated classes.
> What Alexiy wants (I think) is an ability for a life cycle module
> to use its own versions of classes (essentially reverting the delegation
> of class loading).
>
> In other words, changes for one life cycle module should not affect
> the entire app server. I believe this is a fair thing to ask for.
>
> Kedar
>
> Binod wrote:
>> Oleksiy Stashok wrote:
>>
>>> Hi,
>>>
>>> im asking on that, because have my gf lifecycle module working as
>>> tcp listener for Web Services requests,
>>> and for now im working with new jax-ws 2.0.1, which is not embeded
>>> yet to GF.
>>
>> I just discussed this with Vijay.
>>
>> 1. Put appserver/lib/jaxws-update.jar in the classpath-prefix
>> 2. Add
>> <jvm-options>-Dcom.sun.enterprise.websvc.useJAXWSRearch=true</jvm-options>
>>
>>
>> This will get to you the new jax-ws 2.0.1 integrated with appserver.
>> - Binod.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>