axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Pavlovich (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Updated: (AXIS-1927) CLONE -WSDL2Java creates strange decorated QNames
Date Wed, 13 Apr 2005 20:55:30 GMT
     [ http://issues.apache.org/jira/browse/AXIS-1927?page=history ]

Matt Pavlovich updated AXIS-1927:
---------------------------------

    Attachment: authSoap.wsdl

When using this WSDL, WSDL2Java prepends the ">" character to the same fields as described
by the original ticket.  I tested latest 1.2RC3 release, nightly build, and built from latest
CVS (04/13/2005 2:14pm CST), but the issue persisted.

> CLONE -WSDL2Java creates strange decorated QNames
> -------------------------------------------------
>
>          Key: AXIS-1927
>          URL: http://issues.apache.org/jira/browse/AXIS-1927
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.1
>  Environment: Java 1.4.2 b28
> Xerces_J1.4.0
>     Reporter: Matt Pavlovich
>  Attachments: authSoap.wsdl
>
> When feeding 
> org.apache.axis.wsdl.WSDL2Java -s -S true
> with the following WSDL:
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:myns="http://bugdemo/myns" targetNamespace="http://bugdemo/myns">
> 	<wsdl:types>
> 		<xsd:schema xmlns:ccnt_vd="verkehrsdaten.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://bugdemo/myns">
> 			<xsd:element name="get">"
> 				<xsd:complexType>
> 					<xsd:sequence>
> 						<xsd:element name="UserName" type="xsd:string"/>
> 					</xsd:sequence>
> 				</xsd:complexType>
> 			</xsd:element>
> 			<xsd:element name="getResponse">"
> 				<xsd:complexType>
> 					<xsd:sequence>
> 						<xsd:element name="Greeting" type="xsd:string"/>
> 					</xsd:sequence>
> 				</xsd:complexType>
> 			</xsd:element>
> 		</xsd:schema>
> 	</wsdl:types>
> 	<wsdl:message name="getMessage">
> 		<wsdl:part name="parameter" element="myns:get"/>
> 	</wsdl:message>
> 	<wsdl:message name="getResponseMessage">
> 		<wsdl:part name="parameter" element="myns:getResponse"/>
> 	</wsdl:message>
> 	<wsdl:portType name="getPort">
> 		<wsdl:operation name="getOperation">
> 			<wsdl:input message="myns:getMessage"/>
> 			<wsdl:output message="myns:getResponseMessage"/>
> 		</wsdl:operation>
> 	</wsdl:portType>
> 	<wsdl:binding name="readBinding" type="myns:getPort">
> 		<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
> 		<wsdl:operation name="getOperation">
> 			<soap:operation soapAction="urn:my-server"/>
> 			<wsdl:input>
> 				<soap:body use="literal"/>
> 			</wsdl:input>
> 			<wsdl:output>
> 				<soap:body use="literal"/>
> 			</wsdl:output>
> 		</wsdl:operation>
> 	</wsdl:binding>
> 	<wsdl:service name="Parkinfo">
> 		<wsdl:port name="Parkinfo" binding="myns:readBinding">
> 			<soap:address location="http://myUrl"/>
> 		</wsdl:port>
> 	</wsdl:service>
> </wsdl:definitions>
> the generated code contains some calls to the QName class
> constructor with strangely decorated Element names, like:
> new javax.xml.namespace.QName("http://192.168.1.23/parkinfo", ">get")
> in the ReadBindingSkeleton.java, but also in other generated code.
> Furtehrmore, the generated deploy.wsdd contains typeMapping elements like:
> 		<typeMapping xmlns:ns="http://bugdemo/myns" qname="ns:>get" type="java:de.sycada.bugdemo.server._get"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""/>
> with the same strange decorator in the qname.
> In nested elements, this leads to qnames like >data>timestamp.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message