Actually, I was using the Eclipse STP with CXF. Do you think its the STP then that's not validating the WSDL?
Thanks. dkulp wrote: > > > If you run wsdl2java with the -validate flag, you get: > > WSDLToJava Error: A document-literal binding in a DESCRIPTION MUST refer, > in > each of its soapbind:body element(s),only to wsdl:part element(s) that > have > been defined using the element attribute. > > > Dan > > > On Friday 26 September 2008 5:32:36 pm jackdawson wrote: >> <?xml version="1.0" encoding="UTF-8"?> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us" >> xmlns:apachesoap="http://xml.apache.org/xml-soap"; >> xmlns:impl="urn:login.safe.two.us" >> xmlns:intf="urn:login.safe.two.us" >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> >> <wsdl:types> >> <schema elementFormDefault="qualified" >> targetNamespace="urn:login.safe.two.us" >> xmlns="http://www.w3.org/2001/XMLSchema";> >> >> <complexType name="TestLoginType"> >> <sequence> >> <element name="eid" maxOccurs="1" >> minOccurs="1" type="xsd:string" /> >> <element name="key" >> nillable="true" >> type="xsd:string" /> >> </sequence> >> </complexType> >> >> <complexType name="TestLoginTypeResponse"> >> <sequence> >> <element name="failedReason" >> nillable="true" type="xsd:string" /> >> <element name="status" >> type="xsd:boolean" /> >> </sequence> >> </complexType> >> >> </schema> >> </wsdl:types> >> >> <wsdl:message name="testLoginRequest"> >> <wsdl:part name="testLoginRequestAttributes" >> type="impl:TestLoginType"/> >> </wsdl:message> >> >> <wsdl:message name="testLoginResponse"> >> <wsdl:part name="testLoginResponseAttributes" >> type="impl:TestLoginTypeResponse"/> >> </wsdl:message> >> >> <wsdl:portType name="LoginServicePortType"> >> <wsdl:operation name="testLogin"> >> <wsdl:input message="impl:testLoginRequest" >> name="testLoginRequest" /> >> <wsdl:output message="impl:testLoginResponse" >> name="testLoginResponse" /> >> </wsdl:operation> >> </wsdl:portType> >> >> <wsdl:binding name="LoginServiceSoapBinding" >> type="impl:LoginServicePortType"> >> <wsdlsoap:binding style="document" >> transport="http://schemas.xmlsoap.org/soap/http"; /> >> <wsdl:operation name="testLogin"> >> <wsdlsoap:operation soapAction="" /> >> <wsdl:input name="testLoginRequest"> >> <wsdlsoap:body use="literal" /> >> </wsdl:input> >> <wsdl:output name="testLoginResponse"> >> <wsdlsoap:body use="literal" /> >> </wsdl:output> >> </wsdl:operation> >> </wsdl:binding> >> >> <wsdl:service name="LoginService"> >> <wsdl:port binding="impl:LoginServiceSoapBinding" >> name="LoginService"> >> <wsdlsoap:address >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"; >> /> >> </wsdl:port> >> </wsdl:service> >> </wsdl:definitions> > > > > -- > Daniel Kulp > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19696717p19725780.html Sent from the cxf-user mailing list archive at Nabble.com.
