Hi, In Tapestry, assets are versioned with the application version appended to the start of all classpath and context assets. This is a great feature because of effective cache and cache invalidation after an application upgrade.
But, problems come when I linked one of these assets before upgrading to a newer version. For example, someone linked the generated URL (http://www.example.org/assets/1.2.3/images/logo.png) from another site (or even in the same site if it is a CMS). The, when the application changes its version, the URL is no longer valid (it should be now http://www.example.org/assets/1.2.4/images/logo.png or so). So, I think the desired behaviour should be to use the version to produce new URL assets in the application, but to ignore it when you make a request for an asset (so, old links will be backward compatible but it will not loose the cache effects). In fact, I notice this problem when, in a CMS like application, I used FCKEditor and its emoticons. When updating the application, all the emoticons images inserted in edited pages were lost… I suppose this could be done with a dispatcher or filter, but is there a reason for Tapestry not doing this by default? Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Versioned-assets-tp5421811p5421811.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
