Currently this is one of the asset shortcoming. Therefore I want to
introduce file assettype (see
https://issues.apache.org/jira/browse/TAP5-423) and later also URL alias
for tapestry core (so you can include statics through another webroot).
Currently there does exist something like URL alias already
(http://www.chenillekit.org/chenillekit-tapestry/apidocs/index.html) so
you could use it for now. But I am trying to introduce this for
tapestry-core also after finishing the filetype asset type.
Britske schrieb:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
