[jbpm-dev] [Design of JBoss jBPM] - Re: sar vs ear packaging

[thomas.diesler@jboss.com]

Alejandro,

anonymous wrote : 
  | The enterprise jar exposes the command service remotely, and the jms messaging / ejb scheduler services locally. If test cases were written in terms of commands (the EjbSchedulerTest actually is) then Cactus would not be needed.
  | 
  | Nevertheless, the web console is not written in terms of commands because it is meant to work either standalone or in tandem with the enterprise jar. Because (a) it relies on the local functionality and (b) it is the only client provided with the distribution, it is not like any other client component. 
  | 

ok, in that case the ear serves an actual purpose and we should stick to it. I'll take JBPM-1717 and do the ear as you suggested.

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

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