Is there any reason you're not using context assets for this? I don't really see the point in putting static content like images in a protected area like WEB-INF and having Tapestry serving them. Just puts more load on the Tapestry servlet when whatever web server you're using could serve them for you.
-----Original Message----- From: Kris Rasmussen [mailto:[EMAIL PROTECTED] Sent: 26 April 2006 20:36 To: tapestry-user@jakarta.apache.org Subject: Why do Private Assets have to be Classpath Resources? Has anyone considered adding a Private context asset, such as one that resides in the WEB-INF/META-INF directory? I don't see why the private asset needs be a classpath asset. We have stylesheet/images files that we want to keep close to configuration files in the WEB-INF directory but there is no easy way of making them available without creating a custom service. I'd appreciate your opinions. Kris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
