Em Wed, 26 Aug 2009 11:10:17 -0300, Onno Scheffers <o...@piraya.nl>
escreveu:
I think not even css-files, js-files and png-files should be whitelisted
by default to be honest. We already have a way of making such files
public: put them in the public web context.
The Tapestry asset feature is used even when you use files from the
context (asset:context:something.jpg). And assets provided by modules
should go on the classpath, otherwise you would have to copy files from
that module and put them in predefined folders, killing the very nice
"drop a JAR in the classpath and it works automatically" feature for
Tapestry.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
