Re: Wrapper style test in WSDL processing?

[Raymond Feng]

Hi,

The operation.getInput() cannot be null to qualify for the wrapper style. 
There must be a part in the input message corresponding to the operation 
name:

input
   --- message
       --- part (only one part)
               --- element (the element name should be the same as the 
operation name)

The element should look like this:

<element name="myMethod">
   <complexType>
       <sequence/> <!-- an empty sequence -->
   </complexType>
</element>

Thanks,
Raymond

----- Original Message ----- 
From: "Simon Laws" <[EMAIL PROTECTED]>
To: "tuscany-dev" <tuscany-dev@ws.apache.org>
Sent: Friday, August 31, 2007 10:34 AM
Subject: Wrapper style test in WSDL processing?


There is a test to determine whether a WSDL operation follows the 
"wrapped"
style in accordance with JAX-WS 2.0 spec.  See 
WSDLOperationIntrospectorImpl
(
http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/interface-wsdl/src/main/java/org/apache/tuscany/sca/interfacedef/wsdl/impl/WSDLOperationIntrospectorImpl.java
)

The code is currently

   public boolean isWrapperStyle() throws InvalidWSDLException {
       if (wrapperStyle == null) {
           wrapperStyle =
               wrapper.getInputChildElements() != null && (
operation.getOutput() == null || wrapper
                   .getOutputChildElements() != null);
       }
       return wrapperStyle;
   }

Which doesn't seem to cater for the case where there may be no input
parameters. I'm diving into this code now to see if I can work out what it
means but if anyone has any insight I would appreciate it.

Needless to say I have a scenario where I am trying to auto generate WSDL
for a method with the signature

String myMethod()

And it's complaining that it's not wrapped.

Simon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]