On Apr 30, 2010, at 5:20 PM, Bill Shannon wrote:
> Tim Quinn wrote on 04/30/10 03:02 PM:
>> (also a reply to Bill's response)
>>
>> I understand that a re-sync will be needed if a remote deployment has
>> failed.
>>
>> I know that, currently, the only way to resync is to restart the
>> server.
>> Has any thought been given to supporting resync while the instance
>> stays
>> up?
>
> Yes, we've thought about it. It's way too hard for now.
> Arbitrary changes could happen to the domain.xml and the
> instance would need to read the new version, compute the
> differences with the old version, figure out how to notify
> all subsystems of the differences, and switch to using the
> new version. And some changes can't be applied while the
> server is up. Oh, and coordinate all that with all the
> operations that may be occurring on the server while this
> is happening.
>
> It's not impossible, it's only software after all, but it's
> not something we're considering for now.
>
Understood. I hope that the implementation for the sync-at-restart-
only approach we're adopting for now be designed at the app-at-an-
instance granularity to enable easy (well, easier) addition of the
other features later.
- Tim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>