What about /tapestry-assets or /t5-assets ?
On Jul 28, 2012, at 9:37 AM, Bob Harner <[email protected]> wrote: > To correct myself, the more common conflict would be with top-level > /asset folders defined by existing Tapestry-based applications. Still, > that should be uncommon and not such a hard problem to get around. > > On Sat, Jul 28, 2012 at 9:36 AM, Bob Harner <[email protected]> wrote: >> Wouldn't the simplest and cleanest approach be to have assets in >> /assets (top level)? I guess the only problem would be the VERY rare >> case of another servlet in the same war that also uses /assets, but >> that problem is easily overcome by setting a tapestry.assets.folder >> symbol (rarely needed) to something else. >> >> tapestry.assets.folder = "" ...... the default for Tapestry 5.3 and earlier >> >> tapestry.assets.folder = "/assets" ..... the default for Tapestry 5.4 and >> later >> >> tapestry.assets.folder = "/myass" ..... setting a custom location (rarely >> used) >> >> On Fri, Jul 27, 2012 at 1:56 PM, Massimo Lusetti <[email protected]> wrote: >>> On Fri, Jul 27, 2012 at 7:26 PM, Howard Lewis Ship <[email protected]> wrote: >>> >>>> In any case, the question is where to put the files; I'm open to >>>> META-INF/assets/ or T5-RESOURCES/assets/ or META-INF/tapestry/assets/ >>>> or TAPESTRY/assets/ or something along those lines. >>> >>> I'm not an expert or have enough experience but I would make then into >>> T5-RESOURCES/assets or something along the way as META-INF somehow >>> seems a stretch. >>> >>> Cheers >>> -- >>> Massimo >>> http://meridio.blogspot.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
