Support for document and documentwrapped web services

Question

List,
Are "document" and "documentwrapped" style web services supported in WSL 8.1 SP1?
The
documentation referenced below [1] [2] indicates that these styles are supported,
but in the
Unsupported Features section of the Web Services overview [3] states the RPC literal
style and
Document encoded style are not supported. It is my understanding that the style
attribute
values of the servicegen ant task map to the SOAP encodings as follows:
RPC -> SOAP RPC
documentwrapped -> SOAP RPC-literal
document -> SOAP document-literal
Is this correct?
Regards,
Kent
[1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
[2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
[3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641

Answer 1

So is it a true statement that if I use the documentwrapped style, I don't have
the restriction
of having only one void method while gaining the scalability and performance benefits
[1] of
SOAP document-literal encoding? Does the documentwrapped style have any restrictions
regarding out and in-out parameters? If so, what is the correct way in Java to
specify a
parameter as "IN" only?
Thanks again,
--Kent
[1] http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
"manoj cheenath" <[email protected]> wrote:
This is correct. In the doc/lit bare case, a
method with no parameter will have an empty
soap envelope. If you look at the schema for
this operation, it will be an empty complexType.
So in the style, you can only have one void
method. WLS tools (servicegen/source2wsdd) do
not enforce this. Which I think is a bug.
Hope this helps,
-manoj
http://manojc.com
"manoj cheenath" <[email protected]> wrote in message
news:[email protected]...
This is correct. In the doc/lit bare case, a
method with no parameter will have an empty
soap envelope. If you look at the schema for
this operation, it will be an empty complexType.
So in the style, you can only have one void
method. WLS tools (servicegen/source2wsdd) do
not enforce this. Which I think is a bug.
Hope this helps,
-manoj
http://manojc.com
"Kent Kvarfordt" <[email protected]> wrote in message
news:[email protected]...
Bruce,
How do the restrictions apply to methods that do not have any paramters?
>>>
I have attached a copy of the weblogic webservice complex example that I
modified
to use
document style encoding and contains two noarg methods, getVersion
and
getAnotherVersion. I also modified the buy and sell methods to take single arguments.
Following are the results from the test web page for a call to getAnotherVersion.
<!--REQUEST.................-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
</env:Body>
</env:Envelope>
<!--RESPONSE.................-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
<n1:buy
xmlns:n1="http://www.bea.com/examples/Trader">getVersion</n1:buy>
</env:Body>
</env:Envelope>
What am I missing? BTW - I am using Weblogic Server 8.1 SP1.
Also, how does the weblogic documentwrapped style map to the SOAP encodings
SOAP RPC, SOAP RPC-literal, and SOAP document-literal? Are the messages encoded
SOAP doc/lit, but the programming model allows for multiple parameters? Is
the documentwrapped style specific to weblogic webservices?
And finally, given Java is a pass by value language, do I need to
do
anything
special to the webservice method signatures to specify the parameters
as
"IN"
parameters?
Thanks for all the help. From looking at the list traffic, your
keeping
busy.
Regards,
Kent
Bruce Stephens <[email protected]> wrote:
Hi Kent,
There are restrictions on the doc/lit style of encoding, such as
the
methods that implement each operation of the Web Service can have only
one parameter and the methods that implement each operation cannot use
out and in-out parameters. The documentwrapped generates a resulting
Web Service operations that can take any number of parameters, although
the parameter values will be wrapped into one complex data type in the
SOAP messages. Manoj has an example of documentwrapped [1].
We do not support rpc/lit. You might want to review this note by Yasser
Shohoud, it explains this in exquisite detail [2]
Regards,
Bruce
[1]
http://manojc.com/?sample14
[2]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/h
tml/rpc_literal.asp
Kent Kvarfordt wrote:
List,
Are "document" and "documentwrapped" style web services supported
in
WSL 8.1 SP1?
The
documentation referenced below [1] [2] indicates that these styles are supported,
but in the
Unsupported Features section of the Web Services overview [3]
states
the RPC literal
style and
Document encoded style are not supported. It is my understanding
that
the style
attribute
values of the servicegen ant task map to the SOAP encodings as
follows:
RPC -> SOAP RPC
documentwrapped -> SOAP RPC-literal
document -> SOAP document-literal
Is this correct?
Regards,
Kent
[1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
[2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
[3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641