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.
Oh, that's what the InjectObjectWorker does? It caches and reuses the
objects after it gets them for the first time?
Then I agree, that sounds dangerous... That should probably be changed,
unless doing so would break something else on the Hivemind/Tapestry side
of things...
MARK
-----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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
