A correction: The WSDL is treated by JAX-WS as doc-literal-wrapper style.
JAX-WS doesn't require the response element to be named as <op>Response.
So the problem is the tmpVar value.
Thanks,
Raymond
--------------------------------------------------
From: "Raymond Feng" <[email protected]>
Sent: Wednesday, July 01, 2009 1:55 PM
To: <[email protected]>
Subject: Re: BPEL Sample - Does anyone think it is Correct???
Hi,
There are a few issues here:
1) The helloworld.wsdl is not really a doc-lit-wrapped style, so the
HelloWorld java interface is not really compatible with the WSDL unless it
is annotated with bare style.
@SOAPBinding(parameterStyle=ParameterStyle.BARE)
The input/ouput of the WSDL is using the same element. As a result,
wsimport (WSDL2Java) will create JAX-WS Holder. We have yet to port the
support from 1.x to 2.x. Luciano, I remember that you change the wsdl to
be doc-lit-wrapper. Was it for 1.x?
2) I agree with Mike that the response should be a complex type such as:
<hello ...>
<message>Hello World</message>
</hello>
if the hello operation is wrapper style, then Tuscany databinding
framework will get the value of <message> for the response, I.e., "Hello
World".
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <[email protected]>
Sent: Wednesday, July 01, 2009 10:16 AM
To: <[email protected]>
Subject: Re: BPEL Sample - Does anyone think it is Correct???
[[SNIP]]
Ant,
What does the output response message look like in the BPELInvoker, just
after the invocation completes?
In my opinion tmpVar will not be a string, but a string wrapped by the
hello and message elements.
To get the string out, you must do the unwrapping, eg with an XPath
expression such as the one I used in my note...
Yours, Mike.
