Shamelessly ripped from the 4.0-beta-4 documentation:
"Property: org.apache.tapestry.asset.dir, org.apache.tapestry.asset.URL [..] NOTE:Due to changes in Tapestry, these are no longer needed. Issues with security and performance have been fixed in Tapestry 4.0, allowing private assets to be accessed with zero configuration."
So, it appears there's no longer a need for doing what you want to do. Or else I'm misunderstanding you - very likely - and you can just disregard this whole message. : )
-Filip Alan Chandler wrote:
I have asked this question several times before but never received an answer. Now I have got to the point where all my work-arounds don't seem to hack it, so I NEED to ask again.How do I get assets pushed into the correct path so that they can be served statically by my web server. There used to be two tapestry configuration parameters (org.apache.tapestry.asset.dir, org.apache.tapestry.asset.URL) to do this, but they seem to have disappeared in the latest version of the usersguide. (And I couldn't find out how to use these either!).
smime.p7s
Description: S/MIME Cryptographic Signature
