Well, problem solved. As I mentioned, the warning disappeared when I got rid of the source attribute in my <Context> element. My real problem, where Tomcat didn't seem to be publishing my web project, appears to have been caused at least partly by Eclipse adding the src/main/webapp folder to the Java build path. I could have sworn that I checked for this earlier, but either I didn't actually check or else there was another factor which I never properly identified but somehow fixed at some point.
-August -----Original Message----- From: Dwight, August Sent: Thursday, September 30, 2010 6:23 PM To: Tomcat Users List Subject: RE: warning: Setting property 'source' [...] did not find a matching property. > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Thursday, September 30, 2010 1:42 PM > Subject: RE: warning: Setting property 'source' [...] did not find a matching > property. >> I have no build errors or runtime errors. > > Are you looking at *all* of the Tomcat logs when you make that statement? catalina.*.log and localhost.*.log are both clean. > What does Tomcat's manager app say about the state of your webapp? > > What happens when you run Tomcat by itself, not under Eclipse? When I run Tomcat by itself, my app works the way it should, and Manager says it's running. > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Thursday, September 30, 2010 12:07 PM> > > > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > > Subject: Re: warning: Setting property 'source' [...] did not find a > > matching property. > > > You're trying to set the "source" attribute on your > > <Context> element. > > Eclipse has the nasty habit of stuffing this illegal attribute there > automatically. Another reason not to > run Tomcat under Eclipse. If there's a convenient way to do all of the things I need to do without running Tomcat through Eclipse, I'd be happy to try it. I never found a good setup for external Tomcat that gave me satisfactory debugging and delta publishing options. > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Thursday, September 30, 2010 11:44 AM > 2. Don't put your <Context> in your server.xml. Instead, put it into > your webapp's META-INF/context.xml file. Don't have one? Create one. This is good advice in general, and something I will try to do from now on. I moved the <Context> elements out of server.xml and into META-INF/context.xml, and everything seems to be working properly. However, it did not solve my original problem. I hope to have more time tomorrow to take a more thorough look at what is and isn't happening when I start this server, and why. Thanks for your help and suggestions. -August This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
