War with timestamp not using META-INF/context.xml path
Tomcat 5.5.17 JDK 1.5 I deployed a war through the online manager and it deployed it under the filename instead of the path in the META-INF/context.xml of the war. So my war is mycontext-20070427-0946-sys.war And my context.xml has path=/mycontext in it but it deployed it under mycontext-20070427-0946-sys. I thought it should read the path and deploy it under /mycontext without the timestamp. Shawn
RE: War with timestamp not using META-INF/context.xml path
From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: War with timestamp not using META-INF/context.xml path path in the META-INF/context.xml of the war. Neither the path nor the docBase attributes are allowed when the Context element is in META-INF/context.xml. As the doc states, the URI path to the webapp is derived from the name of the .war file. Look here for details: http://tomcat.apache.org/tomcat-5.5-doc/config/context.html - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: War with timestamp not using META-INF/context.xml path
From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: RE: War with timestamp not using META-INF/context.xml path The fourth bullet says this: -if the previous file was not found for this application, in an individual file at /META-INF/context.xml inside the application files Sure sounds like it should to me. You seem to be rigorously ignoring the primary statement in my earlier response: Neither the path nor the docBase attributes are allowed when the Context element is in META-INF/context.xml. Read the description of the path attribute for the Context element: http://tomcat.apache.org/tomcat-5.5-doc/config/context.html - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: War with timestamp not using META-INF/context.xml path
So there is no way to have the war tell the container what context to use other than the filename? Shawn -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 2:23 PM To: Tomcat Users List Subject: RE: War with timestamp not using META-INF/context.xml path From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: RE: War with timestamp not using META-INF/context.xml path The fourth bullet says this: -if the previous file was not found for this application, in an individual file at /META-INF/context.xml inside the application files Sure sounds like it should to me. You seem to be rigorously ignoring the primary statement in my earlier response: Neither the path nor the docBase attributes are allowed when the Context element is in META-INF/context.xml. Read the description of the path attribute for the Context element: http://tomcat.apache.org/tomcat-5.5-doc/config/context.html - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: War with timestamp not using META-INF/context.xml path
From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: RE: War with timestamp not using META-INF/context.xml path So there is no way to have the war tell the container what context to use other than the filename? Correct, unless you manually place the Context element in server.xml, which is strongly discouraged. Why not have your deployment script strip the time stamp off before actual deployment? - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: War with timestamp not using META-INF/context.xml path
We don't use a deployment script. Not sure if we could, it's all secured and isolated. Without the timestamp and the environment in the war name somebody could deploy a war to the wrong environment or an old war. Sounds to me like if it is easy enough to use the filename that you could use the path attribute in META-INF/context.xml just as easy. Shawn -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 2:29 PM To: Tomcat Users List Subject: RE: War with timestamp not using META-INF/context.xml path From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: RE: War with timestamp not using META-INF/context.xml path So there is no way to have the war tell the container what context to use other than the filename? Correct, unless you manually place the Context element in server.xml, which is strongly discouraged. Why not have your deployment script strip the time stamp off before actual deployment? - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: War with timestamp not using META-INF/context.xml path
From: Garner, Shawn [mailto:[EMAIL PROTECTED] Subject: RE: War with timestamp not using META-INF/context.xml path We don't use a deployment script. Not sure if we could, it's all secured and isolated. If you do it by hand, you can do it with a script. Without the timestamp and the environment in the war name somebody could deploy a war to the wrong environment or an old war. Which is why you should be using a script to avoid such human errors. Sounds to me like if it is easy enough to use the filename that you could use the path attribute in META-INF/context.xml just as easy. The path attribute is there primarily for compatibility with the bad old days, where it occasionally caused a great deal of confusion. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: War with timestamp not using META-INF/context.xml path
On 5/3/07, Garner, Shawn [EMAIL PROTECTED] wrote: We don't use a deployment script. Not sure if we could, it's all secured and isolated. Without the timestamp and the environment in the war name somebody could deploy a war to the wrong environment or an old war. Sounds to me like if it is easy enough to use the filename that you could use the path attribute in META-INF/context.xml just as easy. As Chuck mentioned, this is not possible. If you consider using an Ant Build Script or Maven or other (your choice), then you could auto deploy remotely to any location with just the WAR file name minus the timestamp as Chuck mentioned. However, build scripts are out of the scope of this list, but each build tool has their own mailing list - I know Ant has one, probably Maven and others have their own. Shawn -Regards Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
