Hi there, I've got two questions, which might be dependend. I'm developing an application which checks different sources for messages and works with them. There is one component, which is started and which starts and stopps all other services and does the coordination. Basically, this component has to run all the time. If I use a while(true) or a while (boolean) statements, it locks me out from using the Ctrl+C to stop the component. (or is there some kind of a default timelimit?). How do I design my component/application to have one active coordinator/controller component which dispatches, starts and stopps other components? Do I have to use a new Thread. But then, after the main thread is done, it stopps. Maybe I missed the point. Can someone please explain me?
When I start this before mentioned application/component, it is supposed to call on two services, which are listeners that start a new listener thread and registers the listener component with a listener manager. Now the strange thing happens. It starts one listener and registers it, it does it's execution phase (which is not interruptable - from what it looks like) and after that starts the second listener. But at this point it is starting to shut down everything. How can I influence the order of activation/initialization of components? I tried a different order in the ServiceManager.lookup(), I tried different settings (order, activation=startup) in the dependencies and the block.xml. It was always the same. One listener got started before, the other one after the main execution. (One is a DatabaseListener, the other one uses NIO-Channels to listen on). Any clues? Thanks a lot. Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
