[jbpm-dev] [Design of JBoss jBPM] - Re: meeting context

[tom.baeyens@jboss.com]

"camunda" wrote : anonymous wrote : 1) Service API 
  | 
  | This brings to a question I already had in mind: will Commands play a role in future? That could be one form of the API, currently this is the one if you need Remote or Async communication. Some discussions in the past gave me the expressions that a typed API is more preferred from some corners...
  | 
  | On the other hand I like the Commands very much for especially RichClients, and it is a crucial information if Commands will survive or not (for maintainability of existing informations). So this should maybe also thrown in the pot of discussion points around the API?
  | 
  | Or is there already an oppinion we can agree on upfront?
  | 
  | My idea would go in this direction: The Service API's are there as typed interfaces (especially for WebServices). In the implementation for every Method a Command is used, which could be also sent directly without using the API... 

The services method implementations is based on commands.  In other words, the Services are just typed methods that translate into commands.

Commands are then executed by a CommandService.  A chain of command services can put interceptors around the command execution.  Take a look at the environment.cfg.xml in jbpm4. 

So it is an extension of what we were building towards in jBPM 3.

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

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