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).

Any pointers?
Thanks
Adrian

----- Original Message -----
From: Peter Royal <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; Ugo Cei <[EMAIL PROTECTED]>
Cc: Avalon Developers List <[EMAIL PROTECTED]>
Sent: Wednesday, December 05, 2001 4:28 PM
Subject: Re: [Cocoon+Avalon] Adding a new ComponentSelector


> On Wednesday 05 December 2001 11:10 am, Ugo Cei wrote:
> > > You can't! You'll have to add your component to the cocoon.xconf file.
> >
> > Sigh. I suspected it, but I cannot figure out HOW to do it, can you give
> > me a hint?
>
> This is covered in the cocoon-dev archives @ http://marc.theaimsgroups.com
>
> The easiest way is to use the component-instance tag. Ala:
>
> <component-instance class="your.java.Class" role="your.ROLE"/>
>
> -pete
>
> --
> peter royal -> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to