This is partially resolved. Turns out there was a copy of $CATALINA_HOME/conf/[enginename]/[hostname]/(my-context-name).xml around from earlier.
Not sure if I put it there or tomcat did, but removing that and redeploying got it to recognize my custom props. However, It seems like whenever a deploy succeeds (using ant, and <taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/> ), A (my-context-name).xml is created in $CATALINA_HOME/conf/[enginename]/[hostname]. OK, I can see that else how would Tomcat see my context on restart... But, even though reload ( <taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>) says it succeeds, no updates actually take effect. Seems like the session reload is bombing out due to an unserializable field - 0 [main] StandardManager - IOException while loading persisted sessions: java.io.WriteAbor tedException: writing aborted; java.io.NotSerializableException: org.apache.commons.fileupload.Defer redFileOutputStream. Perhaps that's salient, but I'm not sure I want to lose that functionality and I can't see how to to make that commons class Serializable without messing with it directly. Or maybe the point is that changes to META-INF\context.xml must be undeployed / deployed, not reloaded? Maybe; but I'm not even seeing code changes show up on reload. Separately, even though no errors are reported I'm not receiving any mail. Hmmm. Well, I'll have to nap on it. And as much as it may seem like fun, me chatting with myself in public, if anyone can spot my goofs please feel free to chime in. Cheers, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
