The inclusion by components is a side-effect. You can trigger the auto-inclusion without a component by using code that depends on the stack. In particular, if you call JavaScriptSupport.addInitializerCall, JavaScriptSupport.addScript, if you import a library (via annotation or directly via JavaScriptSupport.importJavaScriptLibrary), or you import another stack (by annotation of via JavaScriptSupport.importStack), tapestry will import the full tapestry stack (tapestry.js, prototype.js, etc.) for you.
Robert On Jan 12, 2012, at 1/125:31 PM , Paul Stanton wrote: > Hi all, > > I recently figured out that 'tapestry.js', 'prototype.js' etc is only > included when you have at least one tapestry component within a tml. > > I can't find where this logic takes place however. > > I need to make use of prototype and tapestry js on a page which does not have > any tapesry components and want to figure out the simplest way of including > them. > > Thanks, Paul. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
