for speed reasons, etc. I would like apache httpd to handle css,js and images instead of tomcat Of course apache httpd doesn't know of the resources bundled in the tapestry webapp.
For those of you who are using tapestry with tomcat and a apache httpd frontend: I'm interested in knowing what kind of (automatic) deployment setup you are using to get the assets in a folder apache httpd can read. Of course this eliminates tapestry being able to manage the assets. WOuld there be anything I'm missing out what tapestry can do, what can't be done by apache httpd? Is there any other reasons why I should forget this setup as soon as possible? Thanks, Britske -- View this message in context: http://www.nabble.com/T5%3A-accessing-assets-files-using-apache-httpd-instead-of-tomcat-tp22229014p22229014.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
