Hi there, today I stumbled over a design question. I need some form of listeners, which check periodically a database or network inputs, retrieve events and put it in a queue. Another process has to gather all the events from this single queue and dispatch the processing for the events. Thess are basicly while(true) things. After implementing the while(true) in a start() method, I found out, I couldn't use the Ctrl+c anymore (e.g when it was cycling through exceptions). Merlin just didn't react. Then I thought, try a System.exit call. The system stopped alright, but locked up.
After searching the list archive I found out I needed to spawn a thread. But since the class that implements the runnable isn't originally started by merlin, I have to invoke the initialization stages myself and pass all the info so I can use the potential of lookup and the like. Is there an easy or standard way how to implement/design components, which have to run the entire lifetime of the container and are supposed to exist only once? Ciao Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
