I've developed a component (using many Avalon classes/interfaces) that will manage background tasks for my web application (either by time trigger, or by event via an Action). I thought I should throw it into the cocoon.xconf file for our server. When I do that, it gets configured (I have my own .xconf file), composed then started. Promptly, cocoon calls dispose() on it and it goes away! Look at the cocoon code, it looks like it creates a componentmanager to process the cocoon.xconf component, then cleans it up when that xconf file is finished. That is causing my stuff to get disposed.
So, my questions are, is this where I should put my component (which isn't a traditional sitemap component)? Is there some way to make my component remain running? I know I could ignore the dispose() call, but that isn't playing nice.
Thanks,
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
