Hi Szemere, I am very interested in JBoss, the reason is that we have J2EE applications that we need to combine with our Tapestry web application, and whatever is easier to work with gets my vote!
I have found Jetty to be the best, for development at least. In addition to the hot code replace issues Tomcat has, Tomcat often caches data causing some problems, especially with the partial restarts it does to compensate for class reloading inefficiencies. However Jetty is very lightweight, in eclipse we linked our web application with another J2EE application module running on Tomcat, but we couldn't replicate this setup to run with Jetty. I tested this briefly with JBoss and it also worked but JBoss had far too much baggage and was too slow... if you have any pointers / resources on how can you trim JBoss down, I would love to give it another try! For a production server I swear by Tomcat still, Tomcat 6 is apparantly supposed to be very good performance wise, and the built in connectors like Apache's AJP connector make it easy to configure as reverse proxy to Apache. Please excuse my ignorance, but what added benefit/s does a JBoss wrapped Tomcat bring? thanks, Peter ----- Original Message ----- From: "Szemere Szemere" <[EMAIL PROTECTED]> To: "Tapestry users" <users@tapestry.apache.org> Sent: Thursday, 22 May, 2008 5:16:25 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: t5's version? I can certainly recommend JBoss as a wrapper around Tomcat to solve the classloader issues. It's auto-deploy feature is really effective. You could say it's a little like taking a sledgehammer to crack a nut, but you can slim the sledgehammer (JBoss) down and it does the job effectively and so much better than anything else I've seen. That's our production solution - for dev we also use Jetty, sometimes JBoss-Tomcat. Szemere --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
