Component creation order is controlled exclusively by the container. The actual ordering is established relative to deploy and runtime dependency considerations. All components providing a service are deployed before the service consuming said service. This relates to both the classic runtime dependencies as well as deployment dependencies (e.g. a component providing a lifecycle stage).
You can influence ordering though composition, but at the end of the day is only influence - the container has the final say. To see the startup sequence, you can use the -audit cli option (equivalent to merlin.audit = true). Stephen. > -----Original Message----- > From: PRINCE David [mailto:[EMAIL PROTECTED] > Sent: 27 August 2004 15:41 > To: Avalon framework users > Cc: PRINCE David > Subject: RE: classpath problem > > hi all, > > How to specify component creation order with merlin 3.3.0? > > I have the following component scheme: A->B<-C > A needs B, > C needs B, > A needs C to be created first > But C is optional (plug-in), so there is no dependency between A and C... > > And of course, C is created after A :o( > > thanks > > David > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
