Yes there is a reason. I have my own configuration files for different sites that are serviced by the same tapestry application. I do not want my configuration files to be public, and I also do not want to store the css files that correspond to each individual configuration file in a different directory. Therefore, the private asset would be ideal for this type of use. If performance really were an issue (which in my experience it is not for css files) then I could use the private asset to externalize the files and serve them via Apache. I suppose I could also package my configuration files in the classpath, but it seems more appropriate to keep them with other configuration files in WEB-INF and makes them more accessible for editing in production. This is why I believe private assets should not be limited to classpath assets. Kris
----- Original Message ---- From: Jimmi Dyson <[EMAIL PROTECTED]> To: Tapestry users <tapestry-user@jakarta.apache.org> Sent: Thursday, April 27, 2006 12:48:19 AM Subject: RE: Why do Private Assets have to be Classpath Resources? 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]
