[jboss-dev-forums] [Design of JBoss jBPM] - Re: web services question

[kukeltje]

AAAHHHHHHHHHHH sorry, forgot to do a final preview


ahh ok, The initial trials were handcoded. The best/easiest/standardized (in no order of preference) way of mapping is what I'm looking into. It could be that they can map easisly on commands, but then they have to be aligned. There are 2 options I'm investigating:


  | <command name="startProcess">
  |   <processDefinition>
  |     <name>procName</name>
  |     <version>1.0</version>
  |   </processDefinition>
  |   <variables>
  |     <variable>
  |       <name>damageDate</name>
  |       <value>090906</value>
  |     </variable>
  |     <variable>
  |       <name>amount</name>
  |       <value>191916</value>
  |     </variable>
  |   </variables>
  | </command>
  | 

Personally I'm more in favour of:


  | <startProcess>
  |   <processDefinition>
  |     <name>procName</name>
  |     <version>1.0</version>
  |   </processDefinition>
  |   <variables>
  |     <variable>
  |       <name>damageDate</name>
  |       <value>090906</value>
  |     </variable>
  |     <variable>
  |       <name>amount</name>
  |       <value>191916</value>
  |     </variable>
  |   </variables>
  | </startProcess>
  | 

But this is not so extensible... If we make all elements optional, adding custom commands will be easier in XML, but they still have to be mapped. to either methods that did not exist or add some kind of config to fiond these base on reflection or whatever. Extending commands should benefit all and just be in the code. So I'm looking into the latter solution. I want to generate and XSD first with the commands in mind, but if some coding needs to be done, so be it.

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

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