Thanks Lance. But we have several "@EagerLoads" so we would have to call all their init() methods! On Apr 19, 2012 1:36 PM, "Lance Java [via Tapestry]" < ml-node+s1045711n5651506...@n5.nabble.com> wrote:
> Instead of initializing your @EagerLoad service in it's constructor, you > could add an init() method to the service. > Then you call init() inside a @Startup method after you have initialized > any dependencies. > > http://tapestry.apache.org/registry-startup.html > > Lance. > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://tapestry.1045711.n5.nabble.com/Why-EagerLoad-services-come-before-Startup-methods-tp5651302p5651506.html > To unsubscribe from Why @EagerLoad services come before @Startup > methods?, click > here<http://tapestry.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5651302&code=ZmVycmFubWF5bGluY2hAZ21haWwuY29tfDU2NTEzMDJ8LTIwNzk2MDg1MzA=> > . > NAML<http://tapestry.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >
