There's no point in currently using EJB 3 for the following reasons:
1. Entities are managed through the jBPM libraries, the console by itself has no external
entities, and since JBPM uses hibernate for persistence then we're using automatically
Hibernate
2. We would like to make the console portable as much as possible and since EJB 3 support
in a number of application servers is not yet implemented we resorted to use plain actions
/ pojos instead of SLSB.
3. The integration of the console with the portal is definitely a plus, however that is
delayed with other features until the first release is out. The benefits gained out there
are the delegation of authentication through the security of the portal.
If we were to limit ourselves to JBoss AS then I would definitely go for EJB 3.0 however
we don't want to miss the opportunity of running the console on other application
servers / servlet containers.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139178#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...