cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Geissel" <ageis...@zenark.com>
Subject Re: [Cocoon+Avalon] AutoComposable Components [was Adding a new ComponentSelector]
Date Thu, 06 Dec 2001 14:09:07 GMT
thanks - one question: is initializable called before or after
Composable.compose()?
I also would like access to the ComponentManager at that time.

Adrian

----- Original Message -----
From: Berin Loritsch <bloritsch@apache.org>
To: <cocoon-dev@xml.apache.org>
Sent: Thursday, December 06, 2001 1:51 PM
Subject: Re: [Cocoon+Avalon] AutoComposable Components [was Adding a new
ComponentSelector]


> Adrian Geissel wrote:
>
> > Hi,
> >
> > I have a closely related question, as follows:
> >
> > Is there a mechanism within Cocoon/Avalon to declare a Composable
Component
> > to be Composed during the Cocoon boot routine?
> >
> > I'm thinking of a background processor that lives in parallel to Cocoon,
and
> > is initialized as Cocoon boots and destructed during shut-down (using
the
> > Startable interface).
>
> In Excalibur 4.0 (the official release), ExcaliburComponentManager was
changed
>
> to be Initializable.  When the ECM is initialized, it goes through and
initializes
> all the components that were declared for the ECM.
>
>
>
>
> --
>
> "They that give up essential liberty to obtain a little temporary safety
>   deserve neither liberty nor safety."
>                  - Benjamin Franklin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message