"alex.guizar(a)jboss.com" wrote : There are two entity-based implementations of the scheduler service, one in org.jbpm.scheduler.ejbtimer and the other in org.jbpm.ejb. The descriptor points to the former; the latter is probably the remains of an earlier refactoring. | Up to the last release 3.2.2 the ejb timer service uses an SLSB: one bean on which all the timers are registered. This can become a scalability issue. That's why we (Me and then Fady) implemented the timer entity bean: one bean per timer. "alex.guizar(a)jboss.com" wrote : | The EjbSchedulerService class, introduced in earlier 3.2.x versions, invokes the entity bean, whereas the new EntitySchedulerService class invokes the timer session bean. | I believe the coding of the timer entity bean has been done. I don't know to what extend the timer entity work is finished: * QA-ed * Configurtation in the enteprise ear deployment package * Documentation Alejandro can you verify which of these are done ? "alex.guizar(a)jboss.com" wrote : | The command service interface, home interface and session bean are placed in the org.jbpm.ejb package, whereas the timer entity artifacts are located in org.jbpm.scheduler.ejbtimer. | Any reason for this odd arrangement? If not, I want to rearrange as follows. | Remove the timer entity in org.jbpm.ejb. Move the timer entity in org.jbpm.scheduler.ejbtimer to org.jbpm.ejb. | For backwards compatibility, have EjbSchedulerService invoke the timer session bean. Have EntitySchedulerService invoke the timer entity bean, which better matches its name. The only thing you can take into account is the architectural picture. The services are used inside of the JbpmContext-block. The timer entity bean is only an implementation detail of the EntitySchedulerService. If you take that into account, you can rearrange as you want (as long as it works :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150263#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...