Tim Quinn wrote:
>
> On Nov 16, 2010, at 11:01 AM, Bobby Bissett wrote:
>
>> On Nov 15, 2010, at 7:19 PM, Marina Vatkina wrote:
>>> I usually remove glassfish3/glassfish/domains/domain1/osgi-cache
>>> when I test 3.0->3.1 upgrade.
>>
>> Yep, that's the only advice I have to give, so no cheat sheet Tim.
>> Issue had a brief lifetime here:
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11880
>>
>> Technically, 3.0 -> 3.1 isn't really an upgrade, so you ought to be
>> able to just start a 3.1 server with a 3.0 domain (removing the osgi
>> cache) -- this is the update center use case. On the other hand,
>> running an upgrade on a domain that doesn't need it is supposed to be
>> a no-op, so you can run 'asadmin start-domain --upgrade' on a 3.0 or
>> 3.1 domain if you'd like. (*)
>
> Do we have a completely reliable way to detect if a domain.xml is from
> 3.0.1 or 3.1?
>
> And/or is there any thought to adding an interface such as
> "ConfigurationUpdate" which would be invoked during the first domain
> start-up after an update from 3.0.1 to 3.1, for example?
>
> The issue at hand is that in 3.0.1 some code stored a property under
> an application using a name different from what the on-line help
> describes for the deploy command. That same code has been fixed in
> 3.1, but it'd be nice to convert the property name to the correct one
> rather than just add code in 3.1 to accept either one.
I leave a boolean marker (Jerome's idea during 3.0 time) in the
<timer-service> config during the upgrade, then on the 1st start reset
it to true. I think Hong had an idea what can be checked for in 3.0 vs.
2.x. EJB Timer Service relies on the presence of a file that is not
there in v2.x.
-marina
>
> Thanks.
>
> - Tim
>
>>
>> Cheers,
>> Bobby
>>
>> (*) Which is funny timing because I just realized this morning I
>> hadn't tried that in a while. Was mildly surprised that it worked
>> (except for a minor issue I see in every upgrade).
>>
>>
>> ---------------------------------------------------------------------
>> 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
>