You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/03/17 11:10:58 UTC
Lifetime of XSLTProcessorImpl
Hi,
I just looked at code of the excalibur xmlutil XSLTProcessorImpl.
It seems that it doesn't implement any lifetime interfaces,
so in fact for each lookup a new instance is created.
Is anything preventing us from making it Poolable?
Or did I oversee something?
Regards
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Lifetime of XSLTProcessorImpl
Posted by Leo Simons <le...@apache.org>.
Carsten Ziegeler wrote:
>Hi,
>
>I just looked at code of the excalibur xmlutil XSLTProcessorImpl.
>It seems that it doesn't implement any lifetime interfaces,
>so in fact for each lookup a new instance is created.
>
>Is anything preventing us from making it Poolable?
>
I think not.
cheers!
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Lifetime of XSLTProcessorImpl
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Peter Royal wrote:
>
> On Monday, March 17, 2003, at 05:10 AM, Carsten Ziegeler wrote:
> > I just looked at code of the excalibur xmlutil XSLTProcessorImpl.
> > It seems that it doesn't implement any lifetime interfaces,
> > so in fact for each lookup a new instance is created.
>
> Only inside the ECM :)
>
> > Is anything preventing us from making it Poolable?
> > Or did I oversee something?
>
> Nope, go ahead and add Poolable for proper behavior under ECM and thus
> Cocoon. I'm also using that component under Fortress where that
> behavior is specified in metadata rather than in a marker interface.
Ok, I just updated it and fixed some component releases.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Lifetime of XSLTProcessorImpl
Posted by Peter Royal <pr...@apache.org>.
On Monday, March 17, 2003, at 05:10 AM, Carsten Ziegeler wrote:
> I just looked at code of the excalibur xmlutil XSLTProcessorImpl.
> It seems that it doesn't implement any lifetime interfaces,
> so in fact for each lookup a new instance is created.
Only inside the ECM :)
> Is anything preventing us from making it Poolable?
> Or did I oversee something?
Nope, go ahead and add Poolable for proper behavior under ECM and thus
Cocoon. I'm also using that component under Fortress where that
behavior is specified in metadata rather than in a marker interface.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org