Chuck,
Thank you again for your help and being a great resource! I'm sure I'll
have other questions soon.
Thanks again,
Brandon
Caldarale, Charles R wrote:
>
>> From: behofmann [mailto:behofm...@gmail.com]
>> Subject: RE: Serving Multiple Application Versions w
> From: behofmann [mailto:behofm...@gmail.com]
> Subject: RE: Serving Multiple Application Versions within the same
> Context
>
> Could you please point me to some documentation that explains
> how the construct production#1.0 works?
http://tomcat.apache.org/tomcat-6.0-doc/c
behofmann [mailto:behofm...@gmail.com]
>> Subject: RE: Serving Multiple Application Versions within the same
>> Context
>>
>> specifically if the name would be
>> "production#1.0" in context.xml.
>
> If you're talking about the path or docBase attribu
> From: behofmann [mailto:behofm...@gmail.com]
> Subject: RE: Serving Multiple Application Versions within the same
> Context
>
> specifically if the name would be
> "production#1.0" in context.xml.
If you're talking about the path or docBase attributes of
ail.com]
>> Subject: Re: Serving Multiple Application Versions within the same
>> Context
>>
>> would the associated be called "production_1.0"?
>
> Not quite sure what you're asking, or where the underscore came from. The
> element must be in an
> From: behofmann [mailto:behofm...@gmail.com]
> Subject: Re: Serving Multiple Application Versions within the same
> Context
>
> would the associated be called "production_1.0"?
Not quite sure what you're asking, or where the underscore came from. The
element m
Chuck,
Building on your idea on using webapps/production#1.0 as a versioning scheme
and keeping each application version as a separate context, would the
associated be called "production_1.0"? After more thought, I
agree keeping separate contexts. This approach could keep the context in
synch
> From: behofmann [mailto:behofm...@gmail.com]
> Subject: RE: Serving Multiple Application Versions within the same
> Context
>
> My main objective is to have my client's URL not change
> and have any redirection to a different version be
> transparent to them.
Whic
Chuck,
Thank you for the quick informative reply. My main objective is to have my
client's URL not change and have any redirection to a different version be
transparent to them.
What exactly would you recommend? Since I've never seen the
webapps/production#1.0.war approach, I would have to exp
> From: behofmann [mailto:behofm...@gmail.com]
> Subject: Serving Multiple Application Versions within the same Context
>
> While designing this application, I would like the ability to serve
> multiple application versions within the same context.
Do you really want to do that? Wouldn't it be b
10 matches
Mail list logo
