Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <220960766.1100639907584.JavaMail.apache@nagoya>
Date: Tue, 16 Nov 2004 13:18:27 -0800 (PST)
From: =?ISO646-US?Q?S=3Fbastien_Tardif_=28JIRA=29?= <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS-1619) Wsdl2Java do not respect MIME type  for
 "wrapped" document/literal inout parameters.
In-Reply-To: <394378065.1098726526078.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

     [ http://nagoya.apache.org/jira/browse/AXIS-1619?page=3Dhistory ]

S=E9bastien Tardif updated AXIS-1619:
-----------------------------------

    Attachment: diff.txt

The patch following the "procedure for submitting patches". All test suite =
work.

> Wsdl2Java do not respect MIME type  for "wrapped" document/literal inout =
parameters.
> -------------------------------------------------------------------------=
-----------
>
>          Key: AXIS-1619
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1619
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.2RC1
>  Environment: Axis/CVS 9/23/2004
>     Reporter: S=E9bastien Tardif
>  Attachments: diff.txt, docHarbor.wsdl, docHarbor.wsdl, docHarbor.xml
>
> Defect happen when WSDL has those:
> - wrapped document/literal style
> - use Mime type for implementing Soap with Attachment (SwA)=20
> - has operation that need more that one output parameters
> - you want the operation having a "out" parameter like String in "String =
myOperation(int myInt, DataHandler mySwAttachment)
> By default if you don=92t do anything extra in the WSDL, the generated Ja=
va code will will look like this: =93void myOperation(int myInt, StringHold=
er myString, DataHandler mySwAttachment)=94
> So to have the return type as String you have to specify in the WSDL that=
 mySwAttachment is an inout parameter. This can be done by including mySwAt=
tachment in both the input and output definition.=20
> When using RPC/Literal style this is done in the message section like:
> <wsdl:message name=3D"input">
> =09=09<wsdl:part name=3D"myInt" type=3D=94xsd:int"/>
> =09=09<wsdl:part name=3D"mySwAttachment" type=3D"xsd:base64Binary"/>
> </wsdl:message>
> <wsdl:message name=3D"output">
> =09=09<wsdl:part name=3D"myString " type=3D=94xsd:string"/>
> =09=09<wsdl:part name=3D"mySwAttachment" type=3D"xsd:base64Binary"/>
> </wsdl:message>
> As you can see mySwAttachment is duplicated in the input and output. So t=
he Java method will be generated like we want:
> "String myOperation(int myInt, DataHandler mySwAttachment)=94
> But if you use wrapped document/literal style you must only have one part=
 by message element so you need to move the parts to a XML Schema complex t=
ype.
> But when you do that and you duplicate mySwAttachment in the schema/type =
for the list of input and output, you got this when generate the Java metho=
d:
> =20
> =93String myOperation(int myInt, ByteArrayHolder mySwAttachment)=94
> Which mean that Axis recognized the inout parameter but use the wrong typ=
e. The type was supposed to be DataHandlerHolder instead of ByteArrayHolder=
.
> I have attached a real world WSDL, the problem is with operation =93getDo=
cumentAsAttachment=94

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira