Hi Scott I ran into the same problem and I have solved it using Hivemind
utilities, Hivemind utilities has also helped me with other issues like
lazyInitialization errors integrating hibernate with tapestry.
Refer to this post for a solution on how to inject services into pojos
that are used as ASO
RE: PROBLEM SOLVED | Re: Injecting registry services to POJOS
best regards
Raul.
Scott Russell wrote:
I see. I had assumed that a default implementation would have existed that
behaved like hivemind.BuilderFactory, that allowed nested set-object
elements.
-Scott
On Thu 8 December 2005 13:16, Howard Lewis Ship wrote:
What you do is create a custom factory service to create your ASO, and
you inject your dependencies into your custom factory, which can then
pass them on to the ASO.
On 12/7/05, Scott Russell <[EMAIL PROTECTED]> wrote:
I have an application state object, that I would like to have services
set on whenever one is created (ie. standard dependecy injection, not
annotation injection or anything like that)
I tried this in my hivemodule.xml:
<contribution configuration-id="tapestry.state.ApplicationObjects">
<state-object name="client-state" scope="session">
<invoke-factory>
<construct class="com.itglovebox.esmart.state.ClientState">
<set-object property="esmartService"
value="spring:esmartService"/> </construct>
</invoke-factory>
</state-object>
</contribution>
But I am getting an exception when the ASO is first created. So I am
wondering if DI is supported for creating ASOs, and if so, what is the
correct configuration in hivemodule.xml.
regards,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
