https://issues.apache.org/jira/browse/TAPESTRY-1890
On Nov 8, 2007 6:23 AM, Chris Lewis <[EMAIL PROTECTED]> wrote: > I concur. Having a way to selectively filter would be good, but I think > the default behavior should remain as is (auto loading by default). > > chris > > > Ted Steen wrote: > > It would be nice if there was a way to switch on module autoloading, > > with annotation or configuration. > > > > I say this because our application uses the autoloading to power our > > plugin-mechanism. > > And I can imagine that there are others like us, not only using the > > module autoloading for tapestry-modules. > > > > 2007/11/3, lasitha <[EMAIL PROTECTED]>: > > > >> On 11/3/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > >> > >>> The approach I'm moving towards is to add a @SubModule annotation to the > >>> application's module. > >>> > >> +1. > >> > >> This would also be useful in contexts that need only a subset of my > >> production modules, such as testing or prototyping. For example i > >> would like to test my pages via the PageTester without my security > >> layer (tapestry-acegi) getting in the way. Right now i have to stub > >> out and alias portions of tapestry-acegi to do so. With @SubModule i > >> could easily put together just the set of modules needed for different > >> types of tests. > >> > >> Thanks, > >> lasitha > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > > > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
