I've had good luck developing with Jetty 6. Unlike Tomcat, it's quite
easy to set up an "ant jetty" target which launches a server, then
just kill the process and run ant again for the next dev cycle.
Tomcat's hot deploy ought to make this easy, but I've had too many
resource leak, out of memory, and general "Tomcat goes haywire"
issues with the hot deploy to make it good for development. I'm much
happier with Jetty's clean restart approach.
That's not necessarily an endorsement / criticism of either in
production, of course.
Cheers,
Paul
On May 22, 2006, at 1:00 PM, Carl Pelletier wrote:
hi everyone, I'm just starting a new development projet with
Tapestry 4.0 and Hibernate 3.1. I'm looking for the best local
server to install on my computer to make my development.
here are the important point for me:
1- Must be easy to install
2- Easy to deploy with ant and Eclipse.
3- Quick to start and stop.
4- Less configuration possible.
5- Must support JNDI
6- Not to much memory ungry...
Right now, I use Tomcat 5.5.17 with the service installed and I
have some problems. Use about 90mg of memory and is really long to
start and stop.
I'm considaring switching to Jetty 6, is a good idea?
Maybe some theak in tomcat maybe anough..
Please, let me know what you think !
Thanks
Carl Pelletier
P.S> Sorry for bad english, i'm french
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
