I could be wrong, but going with the notion that inject means a hivemind
service I've found that the actual object reference does ~magically~ change
to the correct reference depending on the context and implementation type of
your service. (via proxying I think).
So, if the object in question is a pooled / threaded service object then the
instance you reference should always point to the correct pooled or threaded
instance.
On 4/21/06, Ron Piterman <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> AFAIK all injected objects are passed as arguments to the constructor of
> the page/component class.
>
> so if I use @InjectObject("service-property:...") the property will be
> read once and stored in the page class ! so if the property changes, and
> the injected object will not reflect any changes made since the
> construction of the page/component class, which, assuming one uses a
> pool, might be quite long...
>
> is it really so, or did I understand this wrong and the injected object
> will actually always reflect any changes to the service's property?
>
> Cheers,
> Ron Piterman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
