Hi Kedar
Comments inline.
Kedar Mhaswade wrote:
> Hi Pramod,
>
> Yes, without a doubt. I missed that for a pure web module, without
> which, the web-container wouldn't know what context to open on
> server startup.
>
> In V2, we had a context-root as an attribute of a web-module. Perhaps
> for V3, we should use a property instead, since this is a web-module
> specific thing?
Just wanted to clarify that we should not assume that it is a web-module
specific thing as the contextRoot could also be valid for a Rails
application. I think this is also valid for a Phobos application.
>
> Can you please open an issue-tracker bug to track it?
>
Will do.
Thanks
Pramod
> Regards,
> Kedar
>
> Pramod Gopinath wrote:
>> Hi Kedar
>> Should not the contextRoot information also be persisted ?
>> I have deployed a application that is deployed as :
>> asadmin deploy --name "abc" --contextRoot /def hello
>>
>> Currently the application would work correctly as
>> http://localhost:8080/def after a deployment before the server has
>> been restarted. But after the restart the application can only be
>> accessed at http://localhost:8080/abc/a.
>> This is because the contextRoot information is lost between the
>> server restart and we pick up the name instead.
>>
>> Thanks
>> Pramod
>>
>>
>> Kedar Mhaswade wrote:
>>>
>>> The minimum data required is:
>>> - name
>>> - location
>>> - whether the app/module is enabled
>>>
>>> That should be available for any deployment, I believe.
>>>
>>> Is there other meta-data that you were thinking of persisting to
>>> domain.xml?
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>