except for bind() which is static. Just part of the strategy for deferring, or avoiding, instantiation of the module class.
In retrospect, premature optimization. If I were starting that from scratch, all the methods on a module class would be static. What you see is that the module may be instantiated, and passed a bunch of common dependencies via its constructor, which it can then use inside its service builder methods. However, that idea has been eclipsed by the ServiceBinder approach, and the cost of looking up services is minute. On Feb 6, 2008 11:08 AM, Davor Hrg <[EMAIL PROTECTED]> wrote: > module methods can be both static and instance methods, > you choose ... > > http://tapestry.apache.org/tapestry5/tapestry-ioc/module.html > > Davor Hrg > > > > On 2/6/08, Hilco Wijbenga <[EMAIL PROTECTED]> wrote: > > On Feb 5, 2008 11:19 PM, Davor Hrg <[EMAIL PROTECTED]> wrote: > > > http://wiki.apache.org/tapestry/Tapestry5HowToIocOnly > > > http://wiki.apache.org/tapestry/Tapestry5HowToIocAndHibernate > > > > Oh, nice! I had not noticed these. > > > > Is there a reason that the Module needs to have a *static* > > bind(ServiceBinder)? Why can't this be an instance method? (This > > doesn't relate directly to the wiki, of course, I just noticed it > > again.) > > > > --------------------------------------------------------------------- > > 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] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
