Re: Context path changes in context.xml not working
I did a bunch of googling before posting my question, but never came across that post; thanks for listing it; it appears to be exactly what I need. Dave Caldarale, Charles R wrote: From: David Kerber [EMAIL PROTECTED] Subject: Re: Context path changes in context.xml not working Nobody has any suggestions about setting up a 2-level context path *without* putting it in the server.xml (it works fine in there)? I thought I remembered something about this, and went googling for the issue. Take a look at: http://marc.theaimsgroup.com/?l=tomcat-userm=110989168604231w=2 If you put your Context fragment in conf/[enginename]/[hostname]/dir1#dir2#appname.xml you can access the webapp via http://[hostname]/dir1/dir2/appname, which I think is what you want. Haven't been able to find this in the Tomcat doc yet, but I did test it successfully on 5.5.9. Have no idea if this trick with the # would work on the name of a .war file. - Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Context path changes in context.xml not working
Running Tomcat 5.5.9 on Windows 2000 server. I am trying to change the context path of an application, and it works fine when I put this into my server.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\Pelican\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false/ According to the docs, putting this into the server.xml is not the preferred way, but when I put it into my webapps/SiteData/META-INF/context.xml, it doesn't seem to take effect, even when I stop and restart Tomcat. Is there something I'm missing here? Or is it a bug which will be fixed in a later release. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context path changes in context.xml not working
As mentioned several times on the mailing list, path is no longer read from webapp/META-INF/context.xml. Try placing the context information in: engine-name\hostname\appname.xml under %CATALINA_HOME%\conf or %CATALINA_BASE%\conf if you're using multiple Tomcats served from one binary. If you're using the defaults, then engine-name is Catalina and hostname is localhost. HTH /mde/ --- David Kerber [EMAIL PROTECTED] wrote: Running Tomcat 5.5.9 on Windows 2000 server. I am trying to change the context path of an application, and it works fine when I put this into my server.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\Pelican\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false/ According to the docs, putting this into the server.xml is not the preferred way, but when I put it into my webapps/SiteData/META-INF/context.xml, it doesn't seem to take effect, even when I stop and restart Tomcat. Is there something I'm missing here? Or is it a bug which will be fixed in a later release. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context path changes in context.xml not working
Intended behavior. path attributes are ignored in context xml files. If you'd like to change the name of the webapp, I'd suggest changing the name of the .war file to change it's name. If you aren't working with .war files, change the name of the webapp folder and then the name of it's context xml file located in config/Catalina/localhost. Restart tomcat and you're done. --David David Kerber wrote: Running Tomcat 5.5.9 on Windows 2000 server. I am trying to change the context path of an application, and it works fine when I put this into my server.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\Pelican\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false/ According to the docs, putting this into the server.xml is not the preferred way, but when I put it into my webapps/SiteData/META-INF/context.xml, it doesn't seem to take effect, even when I stop and restart Tomcat. Is there something I'm missing here? Or is it a bug which will be fixed in a later release. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- === David Smith Network Operations Supervisor Department of Entomology College of Agriculture Life Sciences Cornell University 2132 Comstock Hall Ithaca, NY 14853 Phone: 607.255.9571 Fax: 607.255.0939 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context path changes in context.xml not working
I guess I missed that part about paths - thanks for pointing that out. How do I rename things to get the 2-level context path? This is an app I'm migrating from SilverStream to Tomcat, and I don't want to change the url my users use to connect to it. David Smith wrote: Intended behavior. path attributes are ignored in context xml files. If you'd like to change the name of the webapp, I'd suggest changing the name of the .war file to change it's name. If you aren't working with .war files, change the name of the webapp folder and then the name of it's context xml file located in config/Catalina/localhost. Restart tomcat and you're done. --David David Kerber wrote: Running Tomcat 5.5.9 on Windows 2000 server. I am trying to change the context path of an application, and it works fine when I put this into my server.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\Pelican\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false/ According to the docs, putting this into the server.xml is not the preferred way, but when I put it into my webapps/SiteData/META-INF/context.xml, it doesn't seem to take effect, even when I stop and restart Tomcat. Is there something I'm missing here? Or is it a bug which will be fixed in a later release. Dave - 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: Context path changes in context.xml not working
Nobody has any suggestions about setting up a 2-level context path *without* putting it in the server.xml (it works fine in there)? Dave David Kerber wrote: I guess I missed that part about paths - thanks for pointing that out. How do I rename things to get the 2-level context path? This is an app I'm migrating from SilverStream to Tomcat, and I don't want to change the url my users use to connect to it. David Smith wrote: Intended behavior. path attributes are ignored in context xml files. If you'd like to change the name of the webapp, I'd suggest changing the name of the .war file to change it's name. If you aren't working with .war files, change the name of the webapp folder and then the name of it's context xml file located in config/Catalina/localhost. Restart tomcat and you're done. --David David Kerber wrote: Running Tomcat 5.5.9 on Windows 2000 server. I am trying to change the context path of an application, and it works fine when I put this into my server.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\Pelican\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false/ According to the docs, putting this into the server.xml is not the preferred way, but when I put it into my webapps/SiteData/META-INF/context.xml, it doesn't seem to take effect, even when I stop and restart Tomcat. Is there something I'm missing here? Or is it a bug which will be fixed in a later release. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context path changes in context.xml not working
Did you try it in: $CATALINA_HOME/conf/engine-name/hostname/appname.xml? /mde/ --- David Kerber [EMAIL PROTECTED] wrote: Nobody has any suggestions about setting up a 2-level context path *without* putting it in the server.xml (it works fine in there)? Dave __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context path changes in context.xml not working
From: David Kerber [EMAIL PROTECTED] Subject: Re: Context path changes in context.xml not working Nobody has any suggestions about setting up a 2-level context path *without* putting it in the server.xml (it works fine in there)? I thought I remembered something about this, and went googling for the issue. Take a look at: http://marc.theaimsgroup.com/?l=tomcat-userm=110989168604231w=2 If you put your Context fragment in conf/[enginename]/[hostname]/dir1#dir2#appname.xml you can access the webapp via http://[hostname]/dir1/dir2/appname, which I think is what you want. Haven't been able to find this in the Tomcat doc yet, but I did test it successfully on 5.5.9. Have no idea if this trick with the # would work on the name of a .war file. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
