On Aug 18, 2009, at 10:50 AM, Jagadish Prasath Ramu wrote:
> Copying dev_at_GF.
>
> Hi Jerome,
>
> <resources> & <resource-ref> elements of domain.xml in v2 will work
> fine
> in v3
> In v3, new attributes are added, but none are mandatory. So, we assume
> that no upgrade functionality is needed here. Please confirm.
confirmed.
> Thanks,
> -Jagadish
>
>
>
> On Tue, 2009-08-18 at 13:09 -0400, Rebecca Searls wrote:
>> Send this question to dev_at_glassfish.dev.java.net.
>> Someone on the core team should be able to answer this.
>>
>>
>> On 08/18/09 13:14, Jagadish Prasath Ramu wrote:
>>> Hi Rebecca,
>>>
>>> Just to clarify :
>>>
>>> <resources> & <resource-ref> elements of domain.xml do not undergo
>>> any
>>> change between v2 and v3 (In v3, new attributes are added, but
>>> none are
>>> mandatory).
>>>
>>> So, we assume that no upgrade functionality is needed here as the
>>> configuration of <resources> & <resource-ref> in v2 will work
>>> fine in
>>> v3.
>>>
>>> Thanks,
>>> -Jagadish
>>>
>>>
>>> On Tue, 2009-08-18 at 12:43 -0400, Rebecca Searls wrote:
>>>> V3 (core) does not distinguish between in-Place and side-by-side
>>>> upgrade.
>>>> It alters the domain (domain.xml) file presented to it via the
>>>> start-domain cmd.
>>>> The upgrade Tool utility, asupgrade, handles backing-up the
>>>> source domain and/or
>>>> copying the domain to a new location. V3 (core) services do not
>>>> deal with
>>>> in-place verses side-by-side issues.
>>>>
>>>>
>>>>
>>>> On 08/18/09 12:31, Shalini Muthukrishnan wrote:
>>>>> Hi Rebecca,
>>>>>
>>>>> The Jdbc/Connector connectionpool/resource elements have not
>>>>> undergone
>>>>> much of a change but for some additional attributes. I referred
>>>>> to the
>>>>> UpgradeService done by the applications element in
>>>>> org.glassfish.config.support.UpgradeService and also the Logging
>>>>> related
>>>>> upgrade service. They seem to take care of the inplace upgrade
>>>>> cases.
>>>>>
>>>>> As in, the applications element already existent in the old
>>>>> domain.xml
>>>>> is removed and replaced by a new child with ported attribute
>>>>> values
>>>>> created under the parent. How is this done for a Side by Side
>>>>> upgrade?
>>>>> Does upgrade tool take care of it automatically?
>>>>>
>>>>> One more question i had was related to the jdbc-connection-pool
>>>>> elements. There are only certain additional attributes. Would
>>>>> there be a
>>>>> need for upgrade at all in inplace upgrade case? If so, would
>>>>> each of
>>>>> the resource elements be removed and recreated again with the
>>>>> values
>>>>> from old server?
>>>>>
>>>>> Thanks,
>>>>> Shalini.
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>