Hi, tried that and duplicated the issue, this is the same issue as in 5.2.6, that's the reason I use Robert's AssetProtectionDispatcher, looks like 5.3 and 5.2.6 handle this same way, have tried your code and it works. hope Robert will have his AssetProtectionDispatcher ready for 5.3 as well.
Thanks, angelo lprimak wrote > > You can still get a directory listing of assets, but you can't access them > directly. > I have a fix in the flowlogix library for this, but perhaps I should file > a JIRA... > > > On Dec 7, 2011, at 8:08 AM, Robert Zeigler wrote: > >> I don't think so. Tapestry's default mechanisms are better now. I think >> my Dispatcher is still a bit more stringent and a bit more >> configurable/flexible, but you shouldn't need it. That said, I will >> still go ahead and migrate the service to 5.3 for those who wish to >> continue using it. >> >> Robert > > > -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-3-do-we-still-need-AssetProtectionDispatcher-tp5055048p5057376.html Sent from the Tapestry - User 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
