Hello,
I'm using WO 5.4.1 with an app deployed as a servlet on Tomcat
6.0.14. Last night I deployed an updated version of the app. This is
what I did:
1. I used Tomcat's HTML manager app to stop the old app and undeploy
the old app.
2. I copied the WAR into $TOMCAT/webapps.
3. Tomcat picked up the new WAR, unpacked it and started the app.
4. The new app ran as expected with one exception: it was displaying
the old app's version number string.
The version number string is built from some properties in
Properties. I checked Properties: it had the new version numbers. I
grepped the entire directory tree for "app.version", the prefix of the
property names: it only appeared in Properties with the new version
numbers. Stumped, I stopped and restarted Tomcat---the new version
number string was displayed as expected.
I can only assume that because the JVM itself wasn't cycled in steps
1-3 above that the new app was getting the old numbers from the JVM's
System properties that were retained from the previously running app.
But why weren't the properties re-read as the new app started up, over-
writing the old properties in the JVM's System object? Is this
expected behaviour? Do I really need to cycle Tomcat every time I've
updated something in Properties? That seems heavy-handed---I must be
doing something wrong.
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
