[jbpm-dev] [jBPM Development] - Re: Some bugs and feature requests on jBPM 4.1

[jbarrez]

"kukeltje" wrote : "jbarrez" wrote : 
  |   | "camunda" wrote : 
  |   |   | 8. Support EJB3 Entities as process variables
  |   |   | I think this is a pretty important feature, since a lot of projeects start with EJB3 today. Since Tom fixed a bug in the binding code, I think I can go ahead with that. Will post something as soon I had time to work on it again. If anybody else putting effort into this, please let me know!
  |   |   | 
  |   | 
  |   | The idea is to have a native activity for EJB3 invocations. If im correct, it was scheduled for 4.3.
  |   | 
  | 
  | Isn't there a difference between EJB3 invocations (SFSB, SLSB) and Entity(beans)? Bernd talks about the latter, while you talk about the former.
  | 
  | In combination with the former, integration with Seam (components) should also have a high priority. Personally I'd not have a separate EJB activity, but extend the java activity in such a way that (component)resolvers are used to find the SLSB/SFSB/Seam component/Springbean by name

Right ... in my head EJB3 = SF/SL session beans and JPA is something else ... probably has to do something with bad EJB2 entity memories. So sorry for not reading the remark correctly.

Anyway. Afaik, the current plan is to extends the java activity with EJB capabilities and not create a new activity type. 

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

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