is there a good way to start a timer bean on deployment?
currently, i am using a servlet, that makes a local lookup on the bean and calls "startup". but, this solution seems a little sketchy and i'm a bit concerned that multiple instances of the timer bean might get started.
is there a better way? possibly using a lifecycle module?
thank you
[Message sent by forum member 'ab11' (ab11)]
http://forums.java.net/jive/thread.jspa?messageID=335103