Jerome Dochez wrote:
>
> On Aug 11, 2009, at 1:26 PM, Marina Vatkina wrote:
>
>> Hi Jerome,
>>
>> Will the called code know that it's an undeploy for upgrade (so that
>> we don't drop the tables) and deploy for it (so that we don't create
>> ones)?
>
> yes, please specify any non default re-deployment options you want to
> have specified for this upgrade redeployment so we make sure it's part
> of the command invocation.
Everything 'table' related (dropandcreate/drop/create/) should be explicitly set
to false.
For the EJB timer service, that in v3 is loaded on demand only, we'll need to
figure out the point at which to alter the table to be v3 compatible.
thanks,
-marina
>
>>
>> thanks,
>> -marina
>>
>> Jerome Dochez wrote:
>>
>>> Hi all
>>> During my last engineering meeting, we talked about upgrade and the
>>> necessity to redeploy applications. After talking to Hong and
>>> experimenting, we have decided to have this redeployment happen
>>> internally during the asadmin start-domain --upgrade call.
>>> This does not change anything for containers as these internal
>>> redeployments will not be any different than a normal redeployment
>>> invoked externally through an asadmin command for instance.
>>> Let me know if you have any questions.
>>> jerome
>>> ---------------------------------------------------------------------
>>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>