[
https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra resolved AXISCPP-458.
--------------------------------
Resolution: Fixed
First let me say that wrapper-style vs. non-wrapper style is not a server-side
only concept. From client perspective, a client can ask for either one, and
the result is whether operation parameters are listed individually, or in one
class/structure. It does not affect the structure of the SOAP document that is
sent or retrieved.
However, even if client asks for wrapper-style, the operation may be ineligible
for wrapper style if it does not follow the rules:
1. "Wrapped" is a form of document/literal, therefore it must follow all
the rules defined for document/literal. When defining a document/literal
service, there can be at most one body part in your input message and at most
one body part in your output message. You do *not* define each method parameter
as a separate part in the message definition. (The parameters are defined in
the types section, instead.)
2. Each part definition must reference an element (not a type) defined,
imported, or included in the types section of the WSDL document. These element
definitions are "wrapper" elements (hence the name of this convention). You
define your input and output parameters as element structures within these
wrapper elements.
3. A wrapper element must be defined as a complex type that is a sequence of
elements. Each child element in that sequence will be generated as a parameter
in the service interface.
4. The name of the input wrapper element must be the same as the operation
name.
5. The name of the output wrapper element should be (but doesn't have to be)
the operation name appended with "Response" (e.g., if the operation name is
"add", the output wrapper element should be called "addResponse").
6. In the binding definition, the soap:binding should specify
style="document" (although this is the default value, so the attribute may be
omitted), and the soap:body definitions must specify use="literal" and nothing
else. You must not specify the namespace or encodingStyle attributes in the
soap:body definition.
The above list was obtained from
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
which succinctly lists the criteria. But in general, the critiera specified
in
I have run all the test cases (after changing them to ensure that input element
has same name as operation name) and things seems to be working OK.
The main routine that made this all possible was SymbolTable's
getOperationParameters() method, which gives an indication whether operation is
eligible for wrapper style or not.
The changes have been put under SVN 673717.
I am marking as resolved and not closed in order to get some test cases in
before I close it.
> Unwrapped not supported.
> ------------------------
>
> Key: AXISCPP-458
> URL: https://issues.apache.org/jira/browse/AXISCPP-458
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - Doc
> Reporter: John Hawkins
> Assignee: nadir amra
> Fix For: current (nightly)
>
>
> Unwrapped WSDl style is not supported. This should be removed from WSDL2Ws.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
