> if you mean context.xml in META-INF -> than nope.
> Tomcat only allows you to change the context path from outside, for
> example from localhost/Catalina/distributeme.xml
Perhaps the maven-tomcat-plugin can offer you an acceptable alternative?
http://stackoverflow.com/questions/2593472/define-s
On 1/6/11 12:05 PM, Leon Rosenberg wrote:
> On Thu, Jan 6, 2011 at 5:45 PM, Wayne Fay wrote:
>>> if you mean context.xml in META-INF -> than nope.
>>> Tomcat only allows you to change the context path from outside, for
>>> example from localhost/Catalina/distributeme.xml
>>
>> The documentation su
On Thu, Jan 6, 2011 at 5:45 PM, Wayne Fay wrote:
>> if you mean context.xml in META-INF -> than nope.
>> Tomcat only allows you to change the context path from outside, for
>> example from localhost/Catalina/distributeme.xml
>
> The documentation suggests (to me) otherwise:
> http://tomcat.apache.
> if you mean context.xml in META-INF -> than nope.
> Tomcat only allows you to change the context path from outside, for
> example from localhost/Catalina/distributeme.xml
The documentation suggests (to me) otherwise:
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html
We don't use Tomca
if you mean context.xml in META-INF -> than nope.
Tomcat only allows you to change the context path from outside, for
example from localhost/Catalina/distributeme.xml
regards
Leon
On Thu, Jan 6, 2011 at 5:20 PM, Wayne Fay wrote:
>> You know by chance how to achieve this in tomcat ? (6 or above).
> You know by chance how to achieve this in tomcat ? (6 or above).
As I already said... context.xml. Check Google for more info. There
are other config files used by other containers.
Wayne
-
To unsubscribe, e-mail: users-unsubs
On Thu, Jan 6, 2011 at 3:49 PM, Justin Edelson wrote:
> On 1/6/11 8:16 AM, Leon Rosenberg wrote:
>>
>> Unfortunately no. You can't set the context-path from within the webapp :-(
>> regards
>> Leon
>
> Um, no. You can certainly do this. There just isn't a standard way to do
> it across containers
On 1/6/11 8:16 AM, Leon Rosenberg wrote:
> On Wed, Jan 5, 2011 at 10:21 PM, Wayne Fay wrote:
>>> The webapp have to be accessed by a specific context-path, e.g.
>>> http://host:port/distributeme/registry/list
>>>
>>> The easiest way to achieve it, is to name the war distributeme.war.
>>
>> Each ap
On Wed, Jan 5, 2011 at 10:21 PM, Wayne Fay wrote:
>> The webapp have to be accessed by a specific context-path, e.g.
>> http://host:port/distributeme/registry/list
>>
>> The easiest way to achieve it, is to name the war distributeme.war.
>
> Each app server has its own way of handling this -- cont
> The webapp have to be accessed by a specific context-path, e.g.
> http://host:port/distributeme/registry/list
>
> The easiest way to achieve it, is to name the war distributeme.war.
Each app server has its own way of handling this -- context.xml,
weblogic, xml, etc. You could also just include a
Understood. So you want your users to download the WAR directly from either
your m2repo (weird) or from a Maven repository tool like Nexus, right?
In that case, I don't think it's a Maven problem. You should consider deploying
your generated war file to a web server like Apache (through
maven
Hello Reynald,
I posted it in my original post.
The webapp have to be accessed by a specific context-path, e.g.
http://host:port/distributeme/registry/list
The easiest way to achieve it, is to name the war distributeme.war.
In other words, for external users its easier to understand:
"Download d
Indeed. Sorry I read the topic too quickly to give a wrong answer ;-)
Leon, why do you explicitly need to install the war file in your m2repo with a
custom name? Couldn't you simply use the one you can find in the target/
folder? Or you can always use the maven-resources-plugin to copy the gen
>-Original Message-
>From: Reynald Borer [mailto:reynald.bo...@gmail.com]
>
>You can modify the finalName tag to change the name of artifact. By default
>it is defined like the following:
>
>
>${artifactId}-${version}
>
>
That only affects what gets created in your "target" directory. Onc
On Jan 4, 2011, at 5:26 PM, Leon Rosenberg wrote:
> Hi,
>
> next day, next problem ;-))
>
> I'm right now fighting with the name that comes out of the war packaging.
> My artifact is a webapp, called distributeme-registry and is a module
> of a larger project. However,
> the automatically gen
Hello Renald,
On Tue, Jan 4, 2011 at 11:53 PM, Reynald Borer wrote:
> Hi,
>
>
> You can modify the finalName tag to change the name of artifact. By default
> it is defined like the following:
>
>
> ${artifactId}-${version}
>
>
thats exactly what I did, and as I wrote before it builds it un
Hi,
You can modify the finalName tag to change the name of artifact. By default it
is defined like the following:
${artifactId}-${version}
Or you can modify it only in the war plugin by changing the warName parameter
(see http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html).
Hi,
next day, next problem ;-))
I'm right now fighting with the name that comes out of the war packaging.
My artifact is a webapp, called distributeme-registry and is a module
of a larger project. However,
the automatically generated client expects it to be accessable under
http://host:port/distr
18 matches
Mail list logo
