dev@glassfish.java.net

Re: V3 : Upgrade Service Questions

From: Jerome Dochez <Jerome.Dochez_at_Sun.COM>
Date: Wed, 12 Aug 2009 00:40:59 -0700

On Aug 11, 2009, at 11:47 PM, Kumar Jayanti wrote:

> Rebecca Searls wrote:
>> Kumar Jayanti wrote:
>>> Hi all,
>>>
>>> Has anyone completed their upgrade service implementation ?. If
>>> yes please pass on the pointers to your code so i can take a look.
>>>
>>> Specifically i have questions like :
>>>
>>> 1. How does the Upgrade Service Access the domain.xml of the
>>> source V2 server?. 2. And can i assume that the domain.xml
>>> entities of the destination V3 server can be injected as usual
>>
>> Look at the Grizzle code.
>> Search for class GrizzlyConfigSchemaMigrator.java in module admin/
>> config-api.
>>
>>
>>> 3. Is there any specific location (module/dir-structure) etc. for
>>> the Upgrade Service. I mean can i for example implement the
>>> Security Upgrade Service inside the security/core module.
>>
>> You must implement the service tag. Look at the Upgrade Service
>> TOI slides
>> on the wiki. http://wiki.glassfish.java.net/Wiki.jsp?page=V3UpgradeDashboard
>> It identifies the API you must implement.
> I understand that we need to implement a HK2 Service, but where
> should i place by java file, can it lie inside the security modules
> or is there a separate repo/module where upgrade tool related code
> should be residing.
the easiest is to place it inside your security module.

jerome

>
> regards,
> kumar
>
>>
>>> 4. Does the upgrade service automatically copy resources under the
>>> domainX/config directory from the source V2 server to the
>>> destination V3 server
>>
>> If there is domain config information that you component requires
>> your service
>> must tranlate that information from the V2 and V3-Prelude to the
>> V3 env.
>>
>>> 5. Where can i find samples and instructions on how to run the
>>> upgrade tool or specifically unit test the Upgrade Service
>>> implementation for my specific module.
>> See the Upgrade Service TOI slide for your options.
>>
>>>
>>> Thanks.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>