From: aguizar <nu...@jb...> - 2005-08-03 18:46:19
|
Anil, The jBPM web service consumption requirements are summarized in the following jBPM process action, which describes an RPC invocation: <ws-invoke endpoint="anyURI" operation="math:add" xmlns:math='urn:example:math'> | <input location="firstNumber">var1</input> | <input location="secondNumber>var2</input> | <output location="result">result</output> | </ws-invoke> - 'math:add' is the qualified name of the RPC operation element. - Attribute 'location' specifies a (XPath) location path relative to the operation element. - The content of each 'input' element is an expression whose value is assigned to the specified location in the input message. Note, the value must be either a primitive type or a DOM element; XML<->data binding must be explicitly performed by the user. - The content of each 'output' element identifies a location that receives the value of the specified location in the output message. A request SOAP envelope we would expect to see is: <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> | <S:Body> | <math:add xmlns:math="urn:example:math"> | <firstNumber>20</firstNumber> | <secondNumber>45</secondNumber> | </math:add> | </S:Body> | </S:Envelope> A possible response SOAP envelope is: <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";> | <S:Body> | <math:addResponse xmlns:math="urn:example:math"> | <result>65</result> | </math:addResponse> | </S:Body> | </S:Envelope> Do you think we can build a portable JAX-WS client that implements this design with the current features of JBossWS? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888251#3888251 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888251 |