I'm relatively new to Avalon, but so far I like it. I've noticed that Merlin is doing strange things for starting up my components - frankly I think the way it interprets the block.xml file is bizarre, but *someone* must think it's reasonable.
In particular, I have a component that implements LogEnabled, Serviceable, Configurable, and Initializable. During the initialize() method, it registers itself with another component it discovered during the service() method. The component is marked as activation='startup' in the block.xml. The problem is that the component is not actually being started at startup time. It's well over 10s after the application is started that the component gets its initialize() method invoked, and the application is fairly small. Any ideas what may be going on here? Is there any better description of how Merlin processes the build.xml file than what's on the site? (Which is hopelessly inadequate.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
