DII call with literal & xsi in SOAP request

[noel.rocher]

I've got a DII client with:

 call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");
 call.setOperationName(new QName(NS_URI, "myService"));
 call.addParameter("arrayOfbyte_1", XSD_BYTEARRAYB64, ParameterMode.IN);
...
call.invoke(new Object[]{myValue});
...

My wsdl exposes a RPC/Literal operation.

And I've got this SOAP request (I'm using the jboss jars to run my client):

...
 <soapenv:Body>
 <ns1:myService xmlns:ns1="http://org.jboss/MyService">
 <arrayOfbyte_1 xsi:type="xsd:base64Binary" >UFFQ0...</arrayOfbyte_1>
 </ns1:myService>
...

It seems that I miss something and encoded is use for my parameter.

[noel.rocher]

More test shows:

doing a client wrapped/literal with DII pointing on a RPC/literal endpoint is working in my case.

 call.setProperty(Call.OPERATION_STYLE_PROPERTY,"wrapped");

[jason.greene]

Yuck, this is definately a bug in the axis call implementation. As a workaround you can cast the Call interface to org.jboss.webservice.client.CallImpl, and then call setOperationUse("literal") on the object. I would be carefull with using wrapped though, you could have unexpected behavior. Would you mind opening a JIRA issue?

Thanks,
-Jason

[jason.greene]

Oh one last thing, make sure you call setOperationUse after you set the operation style (the latter overwrites the setting to encoded).

-Jason

[noel.rocher]

Thanks Jason !

In fact doing a literal/wrapped is a very good workaround for us as wrapped/literal is what we want at the end for our attachments.

Only rpc/literal is possible for the endpoint. So when it will be possible to migrate to JBWS 2 with doc/lit endpoint, our clients will be already OK.

And between rpc/literal & wrapped/literal, only the wsdl is different. But we use DII and SOAP Requests are the same !

All is wonderful in a wonderful world !

[sidazad]

Noel, are DII or dynamic proxy clients supported for document/literal or document style services by JBossWS yet? If so, is there a tutorial on how to write these since I think they require some settings apart from the rpc/literal DII/Dynamic Proxy clients.
Thanks, Sid.

[thomas.diesler]

Yes, the DII as well as dynamic proxy is supported with JBossWS. If you follow the WS4EE client programming model as described in the wiki you should not have a problem.

What is your motivation to use DII?

[sidazad]

I don't have to use a DII Client. A Dynamic Proxy client would be fine for me. But I did follow the tutorial and ended up getting errors in the dynamic proxy. I posted those on :
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63230
I also posted the soap message that is being generated by the client and I suspect it has something to do with the settings related to document/literal style services. I couldn't find on the tutorial whether there is any additiona setup required for dynamic proxies for document literal services (as there is required for DIIs).
Thanks, Sid.

[thomas.diesler]

A generated proxy is configured from the WSDl, which contains the style/use of the WS. There should be no additional configuration needed.