Re: Problems with deployment process using Eclipse + Ant + Tomcat

probably be better off just doing this as dependencies instead: target name=deploy depends=init, build, war, deploy_tomcat, email/ I hope that helps, -- PC Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072

Logging and Deployment best practices

the Service? Or should I hardwire some other location for the logs? + Or use the logging functionality of Tomcat via Logger elements? If so - how do I manage deploying the same webapp to different context paths? + Some other alternative? Thanks for any insights, -- PC Paul Christmann Prior

Re: Logging and Deployment best practices

to read the log4j documentation. I want to stay away from programmatic configuration of log4j, and just use property files. Using an environment variable gives me the flexibility I need. Thanks for your answers! -- PC Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587

Re: Logging and Deployment best practices

Shapira, Yoav writes: Loggers are gone in Tomcat 5.5. One gentle suggestion: Is it possible make a note of that in the server configuration documentation? I was reading http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/logger.html and was just getting interested in them before reading a

Re: Logging and Deployment best practices

Phillip Qin writes: Hi, I don't think the log will go to system32 directory. Try something like this log4j.appender.file.File=${catalina.home}/logs/lciponline_debug.txt It will when I just do this, though: log4j.appender.file.File=lciponline_debug.txt Using the environment variable was

5.0.28 Service Shutdown problem on Windows

to [EMAIL PROTECTED], which seems too generic for that type of error message). -- PC Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

Re: 5.0.28 Service Shutdown problem on Windows

for Tomcat 5.0.28. The issue was first reported in an early 5.0 version, fixed for 5.0.16 or 5.0.19, and now apparently has re-appeared. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Paul Christmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 3:53 PM

Re: Tomcat Manager deploy and undeploy

Phillip Qin wrote: - war is uploaded to $CATALINA/work/Standalone/my.host/manager; - war is unpacked into $CATALIAN_HOME/webapps/myapp; Jacob Kjome wrote: completely false I have to agree with Phillip -- I've seen (and reliably reproduced) this behavior with Tomcat 4.1.24-LE. The only way I

Re: Tomcat Manager deploy and undeploy

??? :( :( What am *I* doing I'd really like to figure out what I've done wrong. Please help -- PC Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072 - To unsubscribe, e-mail: [EMAIL PROTECTED

Re: Tomcat Manager deploy and undeploy

Jacob Kjome wrote: Do you add a META-INF/context.xml file containing your Context ... information with the docBase pointing to myapp.war? No, I've never added that. It was only with this release that I even noticed the documentation that it was possible. But thus far I've never needed it.

Re: deploy in 4.1.24

Aha! I found the solution, though not a completely satisfying explanation. Thought I'd post what I found in case anyone else ever encounters something similar. By changing the unpackWARs attribute of the Host element in my server.xml to false, I got back the behavior I had seen in earlier

deploy in 4.1.24

for deployment (the app works, persisted, etc. etc. etc.). BUT -- the undeploy fails. I can use the remove task to remove the app, though. Is this an intentional change in behavior? If so, is there any case where the undeploy task should (could?) be used? -- PC Paul Christmann Prior Artisans, LLC mailto

Re: deploy in 4.1.24

). deploy.war is the name of the war to deploy (/src/net/build/lib/net.war). The build file (and all properties) worked fine before this upgrade, so I'm truly at a loss. -- PC Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072