[jboss-dev-forums] [Design of JBoss jBPM] - organization of the enterprise module

[alex.guizar@jboss.com]

While working on the jBPM 3 enterprise module I found several items that seem out of place.
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.
The EjbSchedulerService class, introduced in earlier 3.2.x versions, invokes the entity bean, whereas the new EntitySchedulerService class invokes the timer session bean.
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.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150216#4150216

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150216