Re: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Here's my context.xml file: Context displayName=My Web App path= docBase=mywebapp.war reloadable=true useNaming=true debug=5 unpackWAR=true /Context Seems to be not working either. When I access the root context (http://localhost), I still get the Tomcat default page and not my webapp's index page. I'm deploying my webapp on a default Tomcat 5.5.3 setup. I will try this on 5.5.4. Am I missing something here like some configurations on the server.xml or web.xml under $CATALINA_HOME/conf/? The simplest solution, as Nick suggested, is to rename my webapp WAR file to ROOT.war. I'm looking at a solution similar on a typical EAR file deployment on a J2EE app (i.e. Jboss) where I can specify my webapp to use the root context path in the application.xml file. On Fri, 5 Nov 2004 13:00:15 +0100, Nick Pellow [EMAIL PROTECTED] wrote: Hi Jojo, I wanted to do the same as you. I got it to work, when the context path is the empty string . ie. Context path= docBase=myrootapp.war What however was annoying, was that tomcat then unpacks this war in a directory called ROOT. Hence, when you restart tomcat, it deploys the webapp under ROOT with context of /, *and*, the webapp called myrootapp.war with context of /myrootapp . Problem was, that I have my META-INF/context.xml in myrootapp. This seems to cause a lot of confusion for tomcat. The cleanest solution I found, was to call myrootapp.war ROOT.war... I would like to know a neater solution if there is one.. Cheers, nick -Ursprungliche Nachricht- Von: Jojo Paderes [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. November 2004 12:45 An: [EMAIL PROTECTED] Betreff: Setting Context Path of Webapp as Root on Tomcat 5.5.3 Hi, Is there a way to set a webapp to use the root context path in Tomcat 5.5.3. For example, I want to access by webapp named mywebapp by using this url: http://mydomain.com/ instead of this: http://mydomain.com/mywebapp/ In a J2EE EAR file, I can set the webapp to use the root context path by setting the context-root value to /. I'm looking for a similar way on WAR file deployed on Tomcat. I was able to do this by just renaming my webapp to ROOT, but I prefer something else. Any suggestions? regards, jOjO - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Here is what worked for me (Tomcat 3.3.2 ) -- Context path= docBase=webapps/Base debug=0 reloadable=true LogSetter name=Base.log path=logs/Base.log servletLogger=true / /Context /webapps in apps-198.xxx.xxx.xxx.xml in the conf directory. I guess that it can be defferent for tomcat 5.5.3. But we never know! Regards -Original Message- From: Jojo Paderes [mailto:[EMAIL PROTECTED] Sent: Friday, November 05, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: Re: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3 Here's my context.xml file: Context displayName=My Web App path= docBase=mywebapp.war reloadable=true useNaming=true debug=5 unpackWAR=true /Context Seems to be not working either. When I access the root context (http://localhost), I still get the Tomcat default page and not my webapp's index page. I'm deploying my webapp on a default Tomcat 5.5.3 setup. I will try this on 5.5.4. Am I missing something here like some configurations on the server.xml or web.xml under $CATALINA_HOME/conf/? The simplest solution, as Nick suggested, is to rename my webapp WAR file to ROOT.war. I'm looking at a solution similar on a typical EAR file deployment on a J2EE app (i.e. Jboss) where I can specify my webapp to use the root context path in the application.xml file. On Fri, 5 Nov 2004 13:00:15 +0100, Nick Pellow [EMAIL PROTECTED] wrote: Hi Jojo, I wanted to do the same as you. I got it to work, when the context path is the empty string . ie. Context path= docBase=myrootapp.war What however was annoying, was that tomcat then unpacks this war in a directory called ROOT. Hence, when you restart tomcat, it deploys the webapp under ROOT with context of /, *and*, the webapp called myrootapp.war with context of /myrootapp . Problem was, that I have my META-INF/context.xml in myrootapp. This seems to cause a lot of confusion for tomcat. The cleanest solution I found, was to call myrootapp.war ROOT.war... I would like to know a neater solution if there is one.. Cheers, nick -Ursprungliche Nachricht- Von: Jojo Paderes [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. November 2004 12:45 An: [EMAIL PROTECTED] Betreff: Setting Context Path of Webapp as Root on Tomcat 5.5.3 Hi, Is there a way to set a webapp to use the root context path in Tomcat 5.5.3. For example, I want to access by webapp named mywebapp by using this url: http://mydomain.com/ instead of this: http://mydomain.com/mywebapp/ In a J2EE EAR file, I can set the webapp to use the root context path by setting the context-root value to /. I'm looking for a similar way on WAR file deployed on Tomcat. I was able to do this by just renaming my webapp to ROOT, but I prefer something else. Any suggestions? regards, jOjO - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
On Fri, 5 Nov 2004 20:23:30 +0800, Jojo Paderes [EMAIL PROTECTED] wrote: Here's my context.xml file: Context displayName=My Web App path= docBase=mywebapp.war reloadable=true useNaming=true debug=5 unpackWAR=true /Context Seems to be not working either. When I access the root context (http://localhost), I still get the Tomcat default page and not my webapp's index page. I'm deploying my webapp on a default Tomcat 5.5.3 setup. I will try this on 5.5.4. Since the path attribute is redundant information, it is ignored in context.xml files. Same for docBase in many cases. Please do not open a bug report about this, or propose switching back to the old behavior. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Hi Jojo,
You should make sure that you delete the ROOT directory under
${CATALINE_HOME}/webapps .
If you are still seeing the tomcat default page, then this means that
the TOMCAT default ROOT app is still deployed somewhere...
Cheers,
nick.
-Ursprungliche Nachricht-
Von: Jojo Paderes [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 5. November 2004 13:24
An: [EMAIL PROTECTED]
Betreff: Re: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Here's my context.xml file:
Context displayName=My Web App
path=
docBase=mywebapp.war
reloadable=true
useNaming=true
debug=5
unpackWAR=true
/Context
Seems to be not working either. When I access the root context
(http://localhost), I still get the Tomcat default page and not my
webapp's index page. I'm deploying my webapp on a default Tomcat 5.5.3
setup. I will try this on 5.5.4.
Am I missing something here like some configurations on the server.xml
or web.xml under $CATALINA_HOME/conf/?
The simplest solution, as Nick suggested, is to rename my webapp WAR
file to ROOT.war. I'm looking at a solution similar on a typical EAR
file deployment on a J2EE app (i.e. Jboss) where I can specify my
webapp to use the root context path in the application.xml file.
On Fri, 5 Nov 2004 13:00:15 +0100, Nick Pellow
[EMAIL PROTECTED] wrote:
Hi Jojo,
I wanted to do the same as you. I got it to work,
when the context path is the empty string .
ie.
Context path= docBase=myrootapp.war
What however was annoying, was that tomcat then unpacks
this war in a directory called ROOT. Hence, when you restart
tomcat, it deploys the webapp under ROOT with context of /,
*and*, the webapp called myrootapp.war with context of /myrootapp .
Problem was, that I have my META-INF/context.xml in myrootapp.
This seems to cause a lot of confusion for tomcat.
The cleanest solution I found, was to call myrootapp.war ROOT.war...
I would like to know a neater solution if there is one..
Cheers,
nick
-Ursprungliche Nachricht-
Von: Jojo Paderes [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 5. November 2004 12:45
An: [EMAIL PROTECTED]
Betreff: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Hi,
Is there a way to set a webapp to use the root context path in Tomcat
5.5.3. For example, I want to access by webapp named mywebapp by
using this url:
http://mydomain.com/
instead of this:
http://mydomain.com/mywebapp/
In a J2EE EAR file, I can set the webapp to use the root context path
by setting the context-root value to /. I'm looking for a similar
way on WAR file deployed on Tomcat.
I was able to do this by just renaming my webapp to ROOT, but I prefer
something else. Any suggestions?
regards,
jOjO
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Hi Remy, Would this mean that the path and docBase attributes are of no use when configured in the META-INF/context.xml in WAR files? If that is the case, then we need to set these attributes in the $CATALINA_HOME/conf/server.xml if we want to customize the context path of our web apps. regards, jOjO On Fri, 5 Nov 2004 13:41:54 +0100, Remy Maucherat [EMAIL PROTECTED] wrote: Since the path attribute is redundant information, it is ignored in context.xml files. Same for docBase in many cases. Please do not open a bug report about this, or propose switching back to the old behavior. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Remy, the server config reference at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html says, Each such Context MUST have a unique context path, which is defined by the path attribute which implies that we must include the path attribute in a Context, wherever it is configured. Perhaps the docs do need a slight fix to reflect what you say below? Since the path attribute is redundant information, it is ignored in context.xml files. Same for docBase in many cases. Please do not open a bug report about this, or propose switching back to the old behavior. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Hi, Remy, the server config reference at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html We're talking about Tomcat 5.5, not 5.0, and about a specific deployment scenario. Yoav says, Each such Context MUST have a unique context path, which is defined by the path attribute which implies that we must include the path attribute in a Context, wherever it is configured. Perhaps the docs do need a slight fix to reflect what you say below? Since the path attribute is redundant information, it is ignored in context.xml files. Same for docBase in many cases. Please do not open a bug report about this, or propose switching back to the old behavior. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Setting Context Path of Webapp as Root on Tomcat 5.5.3
Hi, Sorry, I sent my earlier post accidentally before finishing it. Hi, Remy, the server config reference at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html We're talking about Tomcat 5.5, not 5.0, and about a specific deployment scenario. But you're right that the 5.5 docs are not updated to correctly reflect this new logic. We had a debate and a couple of implementations as to when to take and when to ignore the path and docBase attributes, i.e. when they are optional and when required. We've yet to update the Context docs, so they are a bit misleading for 5.5 now. A path is of course still required, but the user doesn't have to specify it, as Tomcat will now deduce it in some cases. Yoav says, Each such Context MUST have a unique context path, which is defined by the path attribute which implies that we must include the path attribute in a Context, wherever it is configured. Perhaps the docs do need a slight fix to reflect what you say below? Since the path attribute is redundant information, it is ignored in context.xml files. Same for docBase in many cases. Please do not open a bug report about this, or propose switching back to the old behavior. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
