The reason is mainly historical ...
But i also prefer to keep the best of both world : Spring is for me the
best way to glue the layers of our applications (Tapesty, Hibernate and
AOP for transactions, Web Services, ...) as Tapestry is the best
presentation layer ;-)
James Carman wrote:
Use HiveMind and not Spring. :-) Why are you using Spring to
instantiate/configure your beans? Do you have a compelling reason to use a
different IoC container? Are you using AOP?
-----Original Message-----
From: Stephane Decleire [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 12:34 PM
To: Tapestry users
Subject: Re: InjectSpring initialisation error
No, my Spring bean is a "classic" one.
Do you know a way to bypass this problem ?
James Carman wrote:
This has to do with the way the InjectObjectWorker is implemented. I think
it should be changed to lookup the object each time rather than look it up
once and inject that particular value into the object.
-----Original Message-----
From: James Carman [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 12:22 PM
To: 'Tapestry users'; [EMAIL PROTECTED]
Subject: RE: InjectSpring initialisation error
Are you trying to use a non-singleton Spring bean?
-----Original Message-----
From: Stephane Decleire [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 12:18 PM
To: users@tapestry.apache.org
Subject: InjectSpring initialisation error
It seems that when a Spring bean is injected in a Tapestry page using
@InjectSpring, its initial state is not recovered where the page is
detached.
Is it a known bug ? Is there a way to force the reinitialisation of the
bean ?
Thanks in advance.
--
Stéphane Decleire
05 56 57 99 20
06 63 78 69 06
