Thanks  for the reply. I did readup on Avalon lifecycle doc. And I also implmented the Configurable interface.
But the problem i am facing is that cocoon loads up Components dynamically (i.e) when they are first referred.
What i want is  cocoon to instantiate these components at startup time , not dynamically...
unless I am missing something drastically.
-----Original Message-----
From: [] On Behalf Of Ralph Goers
Sent: Friday, 12 March 2004 11:06 AM
To: ''
Subject: RE: Component initialization at cocoon startup

If you haven’t looked at the Avalon lifecycle documentation you should.  In short, all you have to do is implement the Configurable interface.




-----Original Message-----
From: Viswashanti Kadiyala []
Sent: Thursday, March 11, 2004 3:44 PM
Subject: Component initialization at cocoon startup


Hi all,


I would like to know if there is any way i can get  some of  my components declared in the cocoon.xconf

be instantiated at cocoon startup?