I am not aware of anything like that, but I am not too familiar with
that. If you want no loss of service during application upgrade in
production environment, you can take a look the rolling upgrade
procedure documented here:
http://docs.sun.com/app/docs/doc/821-0182/abdik?l=en&a=view
On 11/1/2010 8:37 PM, cj22 wrote:
> Bummer :(
>
> Well is there a cleaner way to keep a stand alone java client connected
> through a redeploy? My thoughts on how to do this lead to rather painful
> implementations, like having to run every call through a connection retry
> block, which is terribly ridiculous. It would be nice to access the actual
> RCP call under the hood and add reconnect logic there. Is that available?
>
>
>
> Hong Zhang-5 wrote:
>
>> No, we don't support the partial redeployment of the applications...
>>
>> On 11/1/2010 7:27 PM, cj22 wrote:
>>
>>> I have a web module that connects to an ejb. We have embedded the war
>>> into
>>> the ear and it works perfectly. I want to be able to change the servlet
>>> code and redeploy the war, without having to redeploy the entire
>>> enterprise
>>> app. Redeploying the whole thing causes my rich clients to lose their
>>> connection. Attempting to just deploy the war gives unresolved ejb-link
>>> errors, which is expected.
>>>
>>> Is it possible to do this? Any help would be greatly appreciated.
>>>
>>> glassfish 2.1.1, ejb 2.1, jdk 5
>>>
>>> Thanks!
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>>
>
>