Hi Guillaume,
I am friendly with WSDL 1.1 but not with WSDL 2.0.
I had a look at this spec and it seems that rpc style is still alive !
http://www.w3.org/TR/2005/WD-wsdl20-adjuncts-20050803/#styles
So what you are saying is that only document / literal mode is supported
into SM ?
Thanks
Charles
Guillaume Nodet wrote:
The JBI spec does not define anything about the xml content carried by
a NormalizedMessage. JBI mainly uses WSDL 2, so that rpc mode is not
really supported. You should use document encoding.
Usually, binding components will not change the xml content (only
extract it from the incoming message). For a soap request, the full
soap body will be sent in the NormalizedMessage.
Cheers,
Guillaume Nodet
On 4/24/06, Charles Souillard <[EMAIL PROTECTED]> wrote:
Hi all,
it is written in the spec that the NMR only carries a standard XML
format but this format is not standard.
What about ServiceMix ?
In fact I am trying to understand how a received xml document is
converted into the standard format.
I can take an example with a simple helloworld service.
I have caught requests and response sent / received between an axis
client and an axis server
I can see that the xml document could be very different depending on the
style (document / rpc) of the use (literal / encoded) specified in the
wsdl file...
You can find some examples under...
In fact I want to know which kind of message I will receive in my SE.
There are many cases (in fact one for each BC ?)
What about the WS BC ?
client -> WS BC -> NMR -> my SE
Can you tell me if the message is left unmodified or if a
standardisation process is performed by the NMR or the BC ?
document / literal
<initiateHelloWorld xmlns="urn:helloworld:bpel:bsoap">
<name xmlns="">toto</name>
</initiateHelloWorld>
rpc / literal (the first node is a wrapper with the operation name)
<initiate xmlns="urn:helloworld:bpel:bsoap">
<parameters xmlns="">
<name>toto</name>
</parameters>
</initiate>
encoded use will add references into the xml document...
Thanks,
Charles
