The order of operations for EagerLoad is not determined. This could be a bug if it is reproducible. It should apply to all services across all modules.
On Sun, Mar 16, 2008 at 4:30 PM, Martijn Brinkers <[EMAIL PROTECTED]> wrote: > Hi, > > I'm using Tapestry 5 IOC stand alone (ie not using the web stuff). I > have two modules for building my services. Some services need to be > eager loaded so I have added the @EagerLoad annotation and call > performRegistryStartup() after RegistryBuilder.build(). > > The problem I face is that only the services from one module are eager > loaded but both modules have services that need to be eager loaded. It > seems that after eager loading the services of one module eager loading > just stops scanning other modules. > > Is this by design or is this a bug? > > Martijn Brinkers > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
