Yep, its me again asking a question on Tapestry 5 and support for other web server containers than Jetty for the complete techical features as depicted for T5. Up until now I have never had a real answer, so I'm trying my luck again.
On the home page of T5 I read: http://tapestry.apache.org/tapestry5/ "It's more than what you can do with Tapestry ... it's also how you do it! Tapestry is a vastly productive environment. Java developers love it because they can make Java code changes and see them immediately ... no redeploy, no restart!" But somewhere I else I read this (on Tomcat): http://tapestry.apache.org/tapestry5/tomcat.html "Deploying Tapestry applications into Tomcat is relatively easy, with one big caveat: you must not store your Tapestry component classes under WEB-INF/classes. At startup, Tapestry needs to locate all your page and component classes, so that it can match page names in request URLs to page classes. Due to the way Tomcat creates ClassLoaders, this information is not accessible to Tapestry. Fortunately, Maven has an option inside its war plugin, archiveClasses, that changes the packaging; instead of putting compiled classes and resource files in WEB-INF/classes, they are instead placed inside an additional JAR inside WEB-INF/lib. This keeps Tapestry happy at runtime." Doesn't this mean that Tomcat cannot use the great productivity booster of "No redeploy, no restart"? I was told (by Howard) that for OC4J (Oracle's J2EE container) I had to do something similar as for Tomcat - so my guess is that "No redeploy, no restart" is also not feasable on that platform. So, can I conclude from this that T5 has improved a great deal - but not everything will work on servlet containers that are actually used? Thanks, -J. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
