I have attached my wsdl file to this email.
The woden version : 1.0M9. from http://www.apache.org/dist/ws/woden/1.0M9/
Apache XmlSchema version : XMLSchema 2.0 from
http://ws.apache.org/commons/xmlschema20/
Xerces version : Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) from
http://xerces.apache.org/xerces2-j/xml-schema.html
Thanks
Rachna
From
Sagara Gunathunga <[email protected]>
Subject
Re: woden and xerces Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta)
compatibility question
Date
Thu, 28 Apr 2011 19:29:50 GMT
Can you attach your original WSDL file ?
Also provide following details ?
1.) Woden version ?
2.) What are the versions of xml-schema and Xerces jar files on your
classpath ?
Alternatively you can download latest Woden distribution from here [1]
and try to run your program only with Jar files available on Woden
distribution.
[1] - http://www.apache.org/dist/ws/woden/1.0M9/
Thanks !
..................................................................
Rachna Jotwani
Data Advantage Group, Inc.
604 Mission Street
San Francisco, CA 94105
Office: +1.415.947.0400 x222
Fax: +1.415.947.0401
Take the first step towards a successful
meta data initiative with MetaCenter -
the only plug and play, real-time
meta data solution. <blocked::BLOCKED::BLOCKED::http://www.dag.com/>
www.dag.com
<?xml version="1.0" encoding="utf-8" ?>
<description
xmlns="http://www.w3.org/ns/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc";
xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";
xmlns:wsdlx= "http://www.w3.org/ns/wsdl-extensions";>
<documentation>
This document describes the GreatH Web service. Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
</documentation>
<types>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema";
targetNamespace="http://greath.example.com/2004/schemas/resSvc";
xmlns="http://greath.example.com/2004/schemas/resSvc";>
<xs:element name="checkAvailability" type="tCheckAvailability"/>
<xs:complexType name="tCheckAvailability">
<xs:sequence>
<xs:element name="checkInDate" type="xs:date"/>
<xs:element name="checkOutDate" type="xs:date"/>
<xs:element name="roomType" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:element name="checkAvailabilityResponse" type="xs:double"/>
<xs:element name="invalidDataError" type="xs:string"/>
</xs:schema>
</types>
<interface name = "reservationInterface" >
<fault name = "invalidDataFault"
element = "ghns:invalidDataError"/>
<operation name="opCheckAvailability"
pattern="http://www.w3.org/ns/wsdl/in-out";
style="http://www.w3.org/ns/wsdl/style/iri";
wsdlx:safe = "true">
<input messageLabel="In"
element="ghns:checkAvailability" />
<output messageLabel="Out"
element="ghns:checkAvailabilityResponse" />
<outfault ref="tns:invalidDataFault" messageLabel="Out"/>
</operation>
</interface>
<binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
type="http://www.w3.org/ns/wsdl/soap";
wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/";>
<fault ref="tns:invalidDataFault"
wsoap:code="soap:Sender"/>
<operation ref="tns:opCheckAvailability"
wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response"/>
</binding>
<service name="reservationService"
interface="tns:reservationInterface">
<endpoint name="reservationEndpoint"
binding="tns:reservationSOAPBinding"
address ="http://greath.example.com/2004/reservation"/>
</service>
</description>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
