cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject Re: cvs commit: xml-cocoon/src/org/apache/cocoon DefaultComponentManager.java CocoonComponentSelector.java
Date Sun, 04 Mar 2001 14:03:10 GMT

----- Original Message -----
From: Paul Russell <prussell@apache.org>
To: <cocoon-dev@xml.apache.org>
Sent: Saturday, March 03, 2001 6:32 PM
Subject: Re: cvs commit: xml-cocoon/src/org/apache/cocoon
DefaultComponentManager.java CocoonComponentSelector.java


> * Berin Loritsch (bloritsch@apache.org) wrote :
> > WARNING! WARNING! WARNING!
>
> Right, this now fixed. Sorry about that. Is there any documentation
> anywhere about who is actually _responsible_ for maintaining the
> lifecycle of these components?

The Avalon docs (now at http://jakarta.apache.org/avalon)
State that the entity (class/component) that instantiated the object is
responsible
for managing it's lifecycle.

Hence the convenience of using the ComponentFactory for both Factory and
Poolable code.

lookup(...) {
  return factory.newInstance()
}

return(...) {
  factory.decommission(...)
}

The Threadsafe components should only be disposed of when the entity that
created
them is disposed.


Mime
View raw message