Re: [picocontainer-dev] Recursive injection

ComponentMonitor was beefed up some since the 1.x.  Many methods now  
container refs to the scoped PicoContainer the component pertains to  
and the ComponentAdapter holding it.

The intent was to solve the same performance issue for web apps.

It would be possible to have a RecordingComponentMonitor and a  
ReplyPicoContainer that did not require the playing back against a  
'real' PicoContainer instance.  Meaning no repeated addComponent(..)s  
needed, only satisfied getComponent(..)s. Much faster in operation as  
its recording at the constructor/setter level.  There should also be  
less side effects as Konstantin observes.

- Paul

On Jun 19, 2007, at 12:54 AM, Konstantin Priblouda wrote:

>
> --- "Putrycz, Erik" <[email protected]>
> wrote:
>
>>
>> Where could I find the "container recorder"?
>> I'd be curious to see what it caches to improve
>> performance.
>
> org.nanocontainer.reflection.DefaultContainerRecorder
> It is  proxy wrapper for MPC, which intercepts all
> calls to it and stores method invocations in
> array list.
>
> those can be replayed later on another fresh contaienr
> instance - works with all scripting builders,
> but sometimes introduces subtle problems due to
> sharing of constant values.
>
> regards,


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email