axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS-1455) WSDL2Java --server-side doesn't produce wrapped stubs
Date Thu, 17 Feb 2005 17:17:48 GMT
     [ ]
Davanum Srinivas commented on AXIS-1455:


Please take a quick look at org.apache.axis.wsdl.symbolTable.SchemaUtils.isWrappedType method.
It enforces the rules specified in "JAX-RPC spec 1.1 Maintenanace Review 2 Chapter 6 Section
4.1.". Basically it states that 

"an element (a wrapper) must be of a complex type defined using the xsd:sequence compositor
and containing only elements declarations"

In your wsdl, the addition of "any" in Concat complexType violates this rule. Can i close
this issue now?


> WSDL2Java --server-side doesn't produce wrapped stubs
> -----------------------------------------------------
>          Key: AXIS-1455
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: beta-2
>  Environment: XP, JDK 1.4.2_03
>     Reporter: Simon Fell
>     Priority: Minor
>  Attachments: ss.wsdl
> running WSDL2Java --server-side on a doc/literal/wrapped WSDL doesn't produce a wrapped
style stub, you get a sub with classes for the request and response messages. Not sure if
this is a bug or by design.
> for the attached WSDL, i get a server side stub of
> public class ConcatBindingImpl implements com.sforce.soap.bugs.ConcatPortType{
>     public com.sforce.soap.bugs.ConcatResult concat(com.sforce.soap.bugs.Concat parameters)
throws java.rmi.RemoteException {
>         return null;
>     }
> }
> rather than one with the parameters broken out, which is what i'd expect for doc/lit/wrapped,

> public class ConcatBindingImpl implements com.sforce.soap.bugs.ConcatPortType{
>     public String concat(String str1, String str2, String str3, org.apache.axis.message.MessageElement
[] _any) throws java.rmi.RemoteException {
>         return null;
>     }
> }

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message