You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilo Frotscher (JIRA)" <ax...@ws.apache.org> on 2005/07/07 17:26:27 UTC
[jira] Updated: (AXIS-2103) WSDL2Java: Generated doc/lit proxy sends "xsi:type" attributes
[ http://issues.apache.org/jira/browse/AXIS-2103?page=all ]
Thilo Frotscher updated AXIS-2103:
----------------------------------
Attachment: GenericAvailabilityService.wsdl
This WSDL imports a lot of XSDs, which in turn import further XSDs themselves.
WSDL2Java handles these chained imports very well!
BTW: I recently found another bug in WSDL2Java. Usually, when generating a proxy for doc/lit services, WSDL2Java generates
one class for every message that was defined in the WSDL. However, this seems to depend on the value of some of the "name"
attributes in the WSDL. Sometimes, only by modifying the values of these "name" attributes, WSDL2Java generates less classes.
Sounds weird, but it's true. I can't send an example at the moment, will send one later.
> WSDL2Java: Generated doc/lit proxy sends "xsi:type" attributes
> --------------------------------------------------------------
>
> Key: AXIS-2103
> URL: http://issues.apache.org/jira/browse/AXIS-2103
> Project: Apache Axis
> Type: Bug
> Components: WSDL processing
> Versions: 1.2.1
> Reporter: Thilo Frotscher
> Priority: Blocker
> Attachments: GenericAvailabilityService.wsdl
>
> I am using WSDL2Java to generate client proxies from WSDL for a doc/lit service.
> However, the generated proxy code sends SOAP requests that contain "xsi:type" attributes, like so:
> ================
> <soapenv:Body>
> <UploadRoomAvailabilityRequest EchoToken="My Echo Token" timeStamp="2005-07-07T14:20:55.209Z" xmlns="http://www.foobar.com/xml/genRoomAvail/2005/5">
> <TRUST_GenericRoomAvail>
> <hotelCode xsi:type="xsd:string">XXXXXX</hotelCode>
> <RoomAllotment>
> <startDate xsi:type="xsd:dateTime">2005-07-07T14:20:55.209Z</startDate>
> <numberOfDaysAffected xsi:type="xsd:int">1</numberOfDaysAffected>
> <Inventory>
> <roomTypeCode xsi:type="xsd:string">A1K</roomTypeCode>
> <numberAlloted xsi:type="xsd:int">65</numberAlloted>
> <status>open</status>
> <minimumLengthOfStay xsi:type="xsd:int">1</minimumLengthOfStay>
> </Inventory>
> </RoomAllotment>
> </TRUST_GenericRoomAvail>
> </UploadRoomAvailabilityRequest>
> </soapenv:Body>
> ================
> However, this worked fine with Axis 1.2 RC3!!!
> Here's what a proxy sends that was generated with WSDL2Java from Axis 1.2 RC3, using exactly the same WSDL file:
> ================
> <soapenv:Body>
> <UploadRoomAvailabilityRequest EchoToken="My Echo Token" timeStamp="2005-07-07T14:18:25.712Z" xmlns="http://www.foobar.com/xml/genRoomAvail/2005/5">
> <TRUST_GenericRoomAvail>
> <hotelCode>XXXXXX</hotelCode>
> <RoomAllotment>
> <startDate>2005-07-07</startDate>
> <numberOfDaysAffected>1</numberOfDaysAffected>
> <Inventory>
> <roomTypeCode>A1K</roomTypeCode>
> <numberAlloted>65</numberAlloted>
> <status>open</status>
> <minimumLengthOfStay>1</minimumLengthOfStay>
> </Inventory>
> </RoomAllotment>
> </TRUST_GenericRoomAvail>
> </UploadRoomAvailabilityRequest>
> </soapenv:Body>
> ================
> Obviously, the SOAP message sent by the Axis 1.2.1 proxy does not validate anymore against the schema.
> Best Regards,
> Thilo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira