Avoid version number from context root of web application

Question

I've web application. I'm using maven to build this application. I get a war file when i build application: my-service-1.0.0-SNAPSHOT.war. While accessing the services over http, i have to make a call like this:

 http://localhost:8080/my-service-1.0.0-SNAPSHOT/......

I don't want version number in my context name. I'm using tomcat as container. Do i have to set context root for this under Web-Inf as we do it in case of jboss ? Does it depend based on the type of container we use ?

You can set the context path on Tomcat: http://stackoverflow.com/questions/7276989/howto-set-the-context-path-of-a-web-application-in-tomcat-7-0 — Anthony Accioly, Oct 01 '13 at 19:29
And you can also use the `path` configuration if you are using tomcat maven plugin: http://stackoverflow.com/a/7811435/664577 — Anthony Accioly, Oct 01 '13 at 19:35
This should not matter because this is in-place container in Maven. This is not intended for production! — Michael-O, Oct 01 '13 at 19:46
Is there any way to handle it in application itself rather than configuring at container level ? I don't want to rename the war file as suggested using maven (build file name). — Pankaj, Oct 01 '13 at 21:23

Jorge Campos · Answer 1 · 2013-10-01T19:42:01.363

4

Using maven you can set a variable in your pom.xml file to store your final build name and in your war plugin configuration you pass it. Something like this:

<build>
  <finalName>my-service</finalName>
</build>

Then in your plugin configuration:

<plugin>
     <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-war-plugin</artifactId>
     <version>2.0</version>
     <configuration>
           <webappDirectory>/path_to_deploy_folder/${project.build.finalName}.war</webappDirectory>
     </configuration>
 </plugin>

edited Oct 01 '13 at 19:42

answered Oct 01 '13 at 19:35

Jorge Campos

22,647
7
56
87

2

No, this is not theright way. The only right way is by modifying the config of the tomcat maven plugin as layed out by Anthony Accioly. – Michael-O Oct 01 '13 at 19:45
Well since the question is mentioning MAVEN to build the application why this is not the right answer, or, at least a valid one? – Jorge Campos Oct 01 '13 at 20:04
1

I agree with Jorge, if only case is to remove version from url, what are cons of this answer? – iskramac Oct 01 '13 at 21:24
It's a perfectly valid answer, IMO. – Patrice M. Oct 01 '13 at 23:59
@JorgeCampos, it's Maven and **not** MAVEN. – Michael-O Oct 02 '13 at 08:13
@Michael-O Yeah, I know that, i just capitalize to emphasize my point :) – Jorge Campos Oct 02 '13 at 13:58
1

There is **bold** especially for that. – Michael-O Oct 02 '13 at 16:31

score 1 · Answer 2 · answered Oct 01 '13 at 23:39

You did not mention whether you are using maven to deploy into tomcat container. If you're creating a production environment you probably won't be using maven at least for local deployments. In that case I don't think it's a bad idea to rename your war file. For example if you want you webapp root to be at https://mydomain.com/subdomain/myteam/myapp then simply rename my-service-1.0.0-SNAPSHOT.war to subdomain#myteam#myapp.war with '/' being replaced by '#'

Avoid version number from context root of web application

2 Answers2