Hey Rob, Thanks for the reply. In trying some more I realized that with AppFuse 1.x we needed to "prepare" Tomcat for deployment. Is there still a need for this step? If so what changes need to be made to Tomcat?
See below for answers to your questions... ----- "Rob Hills" <[EMAIL PROTECTED]> wrote: > Hi Nathan, > > Nathan Anderson wrote: > > So I finally have my AppFuse 2 (Struts 2 + Hibernate) webapp ready > to deploy to my production server. But I appear to be a bit stuck... > > > > > I'm sure there is some way to have maven 2 deploy for me, but I have > not figured out how yet. So I was just planning on going old school > and copy the .war file to my Tomcat 5.5 webapps directory. [I don't > think it is critical, but I installed Tomcat 5.5 using packages > available for Ubuntu 7.10]. > > > > The problem is it isn't starting up, and this is all that shows up > in the logs: > > > > Nov 15, 2007 7:55:20 AM org.apache.catalina.core.StandardContext > start > > SEVERE: Error listenerStart > > Nov 15, 2007 7:55:20 AM org.apache.catalina.core.StandardContext > start > > SEVERE: Context [/mywebapp] startup failed due to previous errors > > > > So my question is two fold... 1) Any guess what could be causing my > app that was working to not work in this environment? and 2) is there > a better way to deploy my app? > > > Question 1 - could permissions be a problem? Maybe try deploying your > > app using Tomcat's manager interface. That should get around any > filesystem permissions issues and working through that will help for > question 2. My first attempt was to just throw the .war in the webapps folder, but I did deploy via the /manager app on my most recent attempt. The error message above is from the /manager deployed version. I also suspected Java security could be a problem because it is enabled by default for Tomcat on Ubuntu. But disabling Java security made no difference. > Question 2 - I use the Tomcat Maven plugin reasonably successfully on > my > dev Windows server and anticipate using it to deploy to staging and > production Tomcat servers on linux boxes with fewer problems - there's > a > know issue with redeploying apps to Tomcat on windows boxes that I've > > not yet got sorted out - to do with Tomcat/Windows not letting go of > jar > files, but that won't bother you. > > You can find out more about the Tomcat Maven plugin here: > http://mojo.codehaus.org/tomcat-maven-plugin/ > > From memory the docco is OK, but if you have any problems getting it > to > work, let me know and I'll dig out some details from my working > profile. I may be rushing things, but it didn't work immediately for me... It appears to me that the tomcat maven plugin is just using the /manager app, so until I can do it manually I'm not likely to be able to use the plugin to automate deployment. Aside from that I did make a profile and when I tried to run tomcat:deploy I hit an OutOfMemoryError. :/ So I guess I need to solve one problem at a time. For now I'd be happy with just deploying the war manually. > HTH, > > Rob Hills > Waikiki, Western Australia Thanks again, Nathan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
