I see more and more projects moving to EJB3. The stuff is easier to understand and even easier to deploy. Actually only having EJB 2.1 support sometimes let jbpm looks "old-fashioned" (never underestimate the marketing factor!). And as I mentioned, I am asked quite a lot for ejb3.
Since you often include jbpm in your own environment or application ejb 3 offers better support. E.g. extending the beans or adding interceptors is easier. And some stuff seems to be better supported with EJB 3 in respect to clustering.
Currently I am rewriting it anyway, so the question comes to if I should commit it, the effort would be reduced to maintenance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208936#4208936
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208936
in many corporate environments, it will take quite a while before ejb 3 gets adopted.
if we offer ejb 2 beans, developers in those businesses can just deploy them. whereas they might not be able to deploy ejb 3 beans.
ejb 3 is nicer for us to write, but that is not a good argument.
all containers that have ejb3 also can run ejb 2. and we have already ejb 2 versions.
so i don't see the point in spending effort to rebuild our own beans on ejb 3 and by doing so limit the number of environments that jbpm can be deployed in.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208930#4208930
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208930