The name of the config-point is ApplicationInitializers, not ApplicationSpecificationInitializer.
> -----Original Message----- > From: Paul Stanton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 24, 2007 2:27 AM > To: Tapestry users > Subject: Re: Hivemind eager loading of a service which > references tapestry services is not possible > > Thanks Howard, > > I've altered the 'contribution element to the following: > > <contribution > configuration-id="tapestry.init.ApplicationSpecificationInitializer"> > <command > after="tapestry.init.ApplicationSpecificationInitializer" > id="zzz" object="service:application.zzz"/> > </contribution> > > But now I get the error message: > > org.apache.hivemind.ApplicationRuntimeException: Error at > context:/WEB-INF/hivemodule.xml, line 29, column 85: Module > application has contributed to unknown configuration point > tapestry.init.ApplicationSpecificationInitializer. The > contribution has been ignored. > > It seems I don't have visibility of the tapestry > configuration points. > How I declare/reference the configuration point? > > Paul. > > Howard Lewis Ship wrote: > > What you do in this case, where you are reliant on information > > HiveMind doesn't have at Registry creation, is to hook into the > > ApplicationInitializers configuration point: > > > > > http://tapestry.apache.org/tapestry4/tapestry/hivedocs/config/tapestry > > .init.ApplicationInitializers.html > > > > > > On 4/22/07, Paul Stanton <[EMAIL PROTECTED]> wrote: > >> > >> I'm trying to avoid Spring and use Hivemind to manage my Hibernate > >> service. It's pretty basic stuff but one basic feature is proving > >> very hard to achieve: eager load startup. > >> > >> In my case I need to reference WebContext (the tapestry > component) in > >> my initialisation procedure, but it seems to be > 'unresolved' at that > >> point and I get a NullPointerException. > >> > >> As a result, I'm starting to think there is a gap in how > Tapestry and > >> Hivemind are integrated, in that tapestry components cannot be > >> referenced in eager loading services. > >> > >> It's possible that changing service loading order (in > >> ApplicationServlet.init) solves this, and equally possible > that I've > >> missed an obvious alternative. > >> > >> I've got a thread with all the relevant details: > >> > >> > http://www.tapestryforums.com/can-hivemind-call-something-after-all-s > >> et-objects-vt9931.html > >> > > > > --------------------------------------------------------------------- > 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]
