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-set-objects-vt9931.html -- Paul Stanton Gunn Software PH: (02) 9918 3666 (ext 503) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
