Howard,
At present this is all the output I'm getting, I haven't enabled
Log4j/Logging yet though (haven't decided on the best way to do so).
org.apache.hivemind.ApplicationRuntimeException: Unable to construct
service tapestry.init.MasterInitializer: Failure invoking constructor
for class
One possibility is that the service you are contributing does not implement
the correct interface, though I'm pretty sure there should be checks in
place for that. I wrote the ChainBuilder code in HiveMind a couple of years
back!
Basically, your contributions are mixed in with Tapestry's and
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
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
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
