cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers" <>
Subject Re: component lifecycles
Date Tue, 29 Jun 2004 16:48:19 GMT

See below

Jeremy Quinn said:
> On 29 Jun 2004, at 02:39, Ralph Goers wrote:
>> Not to throw a wrench in the works, but if I was to implement
>> something like this (I have, in fact), I would make it ThreadSafe and
>> create a new naming context every time it is accessed.
> OK, I have it create a new Context when you instantiate the Component
> in Flowscript using cocoon.getComponent (EntryManager.ROLE);
> However, that same Context gets re-used for each call you make to the
> Component, until you dispose of it.
> As the Component is pooled (implements Recyclable), each simultaneous
> access gets a new one.
> Is this what you meant ?

No. ThreadSafe components are only created once (there is only a single
instance) and are not pooled so they have much less overhead - but they
have to be written to be threadsafe.
>> Then set the system property that allows the JVM to pool JNDI  LDAP
>> contexts and forget about it.
> This sounds interesting ..... do you have any pointers ?

> Thanks
> regards Jeremy

View raw message