Hong Zhang wrote on 10/16/09 08:14:
> Hi, Vivek
>
>>>> The --contextroot provides kind of namespace to the deployed
>>>> application. The application name is computed from the war file
>>>> name by default. Could --contextroot value not provide --name option
>>>> value in this case and so resolve the name conflict. I am assuming
>>>> --contextroot is a unique value on the running instance.
>>>>
>>> We also have an application name space which requires all application
>>> names are unique, this name space is orthogonal to the context root
>>> name space.
>>>
>> Yes, but point is that they are related - together they are unique
>> values. The point was that they are kind of one and the same in
>> certain cases. By default contextroot is derived from application name
>> and in the case of name conflict if --contextroot is provided and is
>> unique, why not use it for name resolution rather than asking user to
>> provide --name value.
>>
> I think it will be confusing if we use name to assign default context
> root and then use context root to assign default app name. And this only
> applies to standalone web module which means we have to special case web
> module in the app name area also.
I agree. The names have to be unique. The context root shouldn't factor
into that requirement, nor should it effect the default name.