CommonJ TimerManager versus EJB3 TimerService
I have to implement a simple (not clustered) timer for WebLogic and it seems there are two different 'standard' options Timer and Work Manager API (CommonJ) EJB3.0 TimerService Does anyone have any advice on using the CommonJ TimerManager versus using the EJB3 TimerService in WebLogic 10.0? Thank you. TimerService in EJB 3.0 is somewhat limited as compared to CommonJ Timer Manager. For example, it requires boilerplate code and container-specific configuration to implement flexible task scheduling. This was simplified with the introduction of @Scheduled annotation in EJB 3.1. If you are stick