For modules you really have to use Assets because you need to serve them from the classpath. For an app you could just hard code paths but it's harder than using Assets because you have to deal with the context plus they handle compression, expires etc. Lastly you can override the url lookup part and move all your Assets to a CDN.
So like most things in Tapestry it's easier to do it the "right way". -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-s-css-js-coming-from-other-languages-frameworks-tp5662291p5662519.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
