Web service gen'd wrong?

Question

Using JDev 10.1.3.0.4.3673...
The goal of this is to pass an array of objects from a java/oracle web service to a .NET client. I'm posting here because it seems there may be a JDev issue with how a web service is created.
OK, I create a stateless session bean. Also, create a bean defining a drivelayout object; generate it's getters/setters. The session bean has a method that'll take rows from a DB, put the data into a drivelayout object, add that object to an arraylist, then do it for the next row found. I then use toArray to take the data from the Arraylist holding the drivelayout objects then return the array as the method's result..
I then generate a web service for the session bean. No problems gen'ing the service.
If I gen the service as document/literal I'll get a serialization error when I test the service; using the servlet gen'd in OC4J. This "should" work, but...
If I gen the service as document/wrapped I get a correct output; an XML doc indicating an array of drivelayout elements, with the elements of drivelayout. Visual Studio 2003 can create a valid web reference to the web service and parse the data passed in correctly.
The problem is that, for interop, I've been under the impression that doc/literal is supposed to be the way to go.
One strange thing is the WSDL gen'd by JDev does show doc/literal
<binding name="DriveSchedRTNSoapHttp" type="tns:DriveSchedRTN">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="readlayouts">
<soap:operation soapAction="http://createsched//readlayouts"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
Since the whole thing seems to work I guess I'm happy but I'm wondering if something will get "fixed" causing this to break in a future release.
Let me know if you need any supporting docs; code, WSDL, etc.
Thanks

Answer 1

Hi,
I don't think that JDev is generating the service incorrectly. Doc-wrapped is really just a special form of doc-lit, intended to make the input parameters of a procedure call look more like one big single input "document". There's no hard-and-fast way to spot a doc-wrapped service, other than to look at the input message for an operation. If it has one part named parameters, defined by an element rather than a complexType, then you've got a wrapped input.
So I think you should be OK with respect to interoperability. If you have any doubts, then you can use the JDev HTTP Analyzer and WS-I testing tools integration to verify that the WSDL document and SOAP messages sent and received match the WS-I interop standards.
Hope that helps,
Alan.