We're just using the default maven structure for our project, let maven build our eclipse project files (eclipse:eclipse) with wtp-compatibility enabled (-Dwtpversion=1.5) and in the Tomcat settings (dbl-click on the server definition inside eclipse) "Serve modules without publishing" enabled. In most situations this allows us to simply edit our files (java/html/css/gif) save them and go back to the browser to test them. Debugging doesn't work as smooth as this though, hot-deploying while debugging seems to fail and adding a new pages or component requires a server-restart as well :(.
Hope this helps, Martin Howard Lewis Ship wrote:
First off, developing locally using Jetty is a fine idea, even if you can't deploy the same way. In most any servlet container, updating the WAR causes an undeploy/redeploy that is outside of Tapestry's scope to control. Second, there's a whole lot more that Tapestry *could* do if it replaced the servlet container entirely and acted as its own HTTP server (possibly built on Jetty). But this falls into the "boilling the ocean" category. Third, there is unfortunately a lot of vaguness in the servlet API spec. Remy (Tomcat) sees the class loader issue one way, Greg (Jetty) sees it the correct way. I can't emphasis enough: use Jetty for your tight, local write-test-fix cycle (with no deploys, and fairly rare restarts). But using Ant or Maven to package your application normally for deployment. On 9/30/07, Jan Vissers <[EMAIL PROTECTED]> wrote: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]
smime.p7s
Description: S/MIME Cryptographic Signature
