How do Tapestry 3.1 and Hivemind work together (was: Tapestry 3.0 and Hivemind Integration Resources)

["Hensley, Richard" <Ri...@McKesson.com>]

Will Tapestry 3.1 combined with Hivemind be able to support "autowiring" of
page classes? I kind of got the impression along the way that a page and a
component were services offered by a Hivemind registry, but this e-mail
seems counter to that notion.

Richard 

-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com] 
Sent: Tuesday, February 22, 2005 9:20 AM
To: Tapestry users; z@absolutez.net
Subject: Re: Tapestry 3.0 and Hivemind Integration Resources

I've been trying to scratch together a few moments to discuss it on
the HiveMind wiki. Basic approach was:

- OGNL mapping to extract services from a Registry by name
- Add Registry as property of base page (or of engine, or make
Registry the Global object)
- Inject services using <property-specification>'s initial-value attribute.


In Tapestry 3.1, it just looks like this:

<inject property="myProperty" object="service:mymodule.MyService"/>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org