We use Jetty embedded in JBoss. From a developer point of view, I can re-compile my code using maven and copy the war over to my version of JBoss in about 8 seconds. I kill and restart the server in 17 seconds. When I want to debug, I tell Eclipse to connect up to JBoss and everything works. Usually, when I try and deploy to the running VM it complains about trying to put the code back, sometimes it works.
Not ideal, but seems to work fine. Mark J. Stang Senior Engineer/Architect office: +1 303.468.2900 mobile: +1 303.507.2833 Ping Identity -----Original Message----- From: Daniel Jue [mailto:[EMAIL PROTECTED] Sent: Fri 2/16/2007 10:11 AM To: Tapestry users Subject: Re: My crap development environment I use WTP with the integrated Tomcat, and it's fine as long as I don't have a lot of web apps running from it. (takes a couple seconds to start, and restarts when I've changed a java or html/jwc.) It doesn't seem to restart when I change a .css file though; the change is just picked up on a screen refresh. I think I went this route because of the examples I had seen online, espcially Kent Tong's book (Chapter 1). I wouldn't mind trying Jetty if I found a good tutorial. I tried setting up Jetty Launcher last night, but I found out it doesn't yet support Jetty 6. On 2/16/07, Holger Stolzenberg <[EMAIL PROTECTED]> wrote: > I think the WTP approach with the temporary tomcat installation is very good > because you can defined which projects should be started with this tomcat, if > you use one tomcat with sysdeo then all webapps will always be starte. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
