They've come out with a new release -- maybe it works better.
I figured it was worth a try.

> -----Original Message-----
> From: Brain, Jim [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2003 11:21 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Need help with Doc/Lit web service
>
>
> I have the CapeClear one, but when I use it, .NET chokes on the WSDL.
>
> Jim
>
>
> Jim Brain, [EMAIL PROTECTED]
> "Researching tomorrow's decisions today."
> (319) 369-2070 (work)
> SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS
>
>  -----Original Message-----
> From:         Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2003 10:20 AM
> To:   [EMAIL PROTECTED]
> Subject:      RE: Need help with Doc/Lit web service
>
> So obviously it's having trouble doing the import.
> Your import statement looks fine, but imports are tricky.
>
> Are you using a WSDL editor tool? It might help you make sure that
> everything's copasetic. Cape Clear offers a free one.
>
> Anne
>
> > -----Original Message-----
> > From: Brain, Jim [mailto:[EMAIL PROTECTED]
> > Sent: Friday, March 07, 2003 11:14 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Need help with Doc/Lit web service
> >
> >
> > I can try, but it is HUGE (It's the ACORD standard for insurance policy
> > data, and it contains 288 top level elements, and thousands of lower
> > elements)
> >
> > BTW, here is the error wsdl.exe is giving:
> >
> > Schema validation warning: Type
> 'http://ACORD.org/Standards/Life/2:TXLife'
> > is no
> > t declared.
> > Schema validation warning: Type
> 'http://ACORD.org/Standards/Life/2:TXLife'
> > is no
> > t declared.
> >
> > Warning: Schema could not be validated. Class generation may fail or may
> > produce
> >  incorrect results.
> >
> > Error: Unable to import binding 'TXLifeProcessorServiceSoapBinding' from
> > namespa
> > ce 'http://localhost:8080/axis/services/TXLifeProcessorService'.
> >   - Unable to import operation 'impl:processTXLife'.
> > - The datatype 'http://ACORD.org/Standards/Life/2:TXLife' is missing.
> >
> > Jim
> >
> >
> > Jim Brain, [EMAIL PROTECTED]
> > "Researching tomorrow's decisions today."
> > (319) 369-2070 (work)
> > SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS
> >
> >  -----Original Message-----
> > From:       Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> > Sent:       Friday, March 07, 2003 10:12 AM
> > To: [EMAIL PROTECTED]
> > Subject:    RE: Need help with Doc/Lit web service
> >
> > Jim,
> >
> > You might try copying the TXLife type definition from the
> schema directly
> > into your WSDL (rather than importing the schema).
> >
> > For that matter, you might want to remove stuff you don't need:
> > the imports
> > of the encoding schema.
> >
> > Anne
> >
> > > -----Original Message-----
> > > From: Brain, Jim [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, March 07, 2003 11:00 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: Need help with Doc/Lit web service
> > >
> > >
> > > OK, here is an update:
> > >
> > > On #1, the WSDL I started with came from AXIS itself, so it is
> > > dropping the
> > > Exception.  I don't know what schema or namespace to put it
> in (I saw a
> > > previous thread about this being a bug.  Note to developers:
> it is still
> > > broke in RC2)  I switched it to xsd:anyType and it will
> suffice I think
> > >
> > > On #2, I broke it into 2 parts.  The first was to get the
> WSDL from AXIS
> > > (with #1 fix) to spit out code.  I used a variant of Ann's
> > suggestion.  I
> > > set the namespace of the first schema element to the one used by
> > > xmlns:impl
> > > and prepended impl: to the wsdl:parts, wsdl:operations and that
> > got it to
> > > complile (I think this is a bug in the WSDL piece that should be
> > > fixed, but
> > > I will leave that to others to decide)
> > >
> > > Or the second part, I am still stuck.  I did as Anne suggested,
> > and added
> > > the xmlns:tx namespace, imported the schema, and set the
> > element types to
> > > "tx:TXLife", but no dice.  I am attaching the WSDL as currently
> > I have it.
> > > If you replace the tx:TXLife with xsd:anyType, it will compile.
> > >
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <wsdl:definitions
> > > targetNamespace="http://localhost:8080/axis/services/TXLifeProcess
> > > orService"
> > > xmlns="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:apachesoap="http://xml.apache.org/xml-soap";
> > >
> xmlns:impl="http://localhost:8080/axis/services/TXLifeProcessorService";
> > >
> xmlns:intf="http://localhost:8080/axis/services/TXLifeProcessorService";
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> > > xmlns:tns1="http://processing.xmlife.acord.org";
> > > xmlns:tns2="http://xmlife.acord.org";
> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> > > xmlns:tx="http://www.acord.org/Standards/Life/2/";
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> > >   <wsdl:types>
> > >           <schema
> > > targetNamespace="http://localhost:8080/axis/services/TXLifeProcess
> > > orService"
> > > xmlns="http://www.w3.org/2001/XMLSchema";>
> > >                   <import
> > > namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> > >                   <import
> > > namespace="http://www.acord.org/Standards/Life/2/";
> > > location="http://localhost/schemas/TXLife2.7.00.xsd"/>
> > >                   <element name="processTXLife" type="tx:TXLife"/>
> > >                   <element name="processTXLifeReturn"
> > > type="tx:TXLife"/>
> > >                   <element name="fault" type="tns1:ProcessException"/>
> > >           </schema>
> > >           <schema targetNamespace="http://xmlife.acord.org";
> > > xmlns="http://www.w3.org/2001/XMLSchema";>
> > >                   <import
> > > namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> > >                   <complexType name="OLifEException">
> > >                           <sequence>
> > >                                   <element name="hiddenException"
> > > nillable="true" type="xsd:anyType"/>
> > >                                   <element name="message"
> > > nillable="true" type="xsd:string"/>
> > >                           </sequence>
> > >                   </complexType>
> > >           </schema>
> > >           <schema targetNamespace="http://processing.xmlife.acord.org";
> > > xmlns="http://www.w3.org/2001/XMLSchema";>
> > >                   <import
> > > namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> > >                   <complexType name="ProcessException">
> > >                           <complexContent>
> > >                                   <extension
> > > base="tns2:OLifEException">
> > >                                           <sequence>
> > >                                                   <element
> > > name="errorCode" type="xsd:int"/>
> > >                                           </sequence>
> > >                                   </extension>
> > >                           </complexContent>
> > >                   </complexType>
> > >           </schema>
> > >   </wsdl:types>
> > >   <wsdl:message name="ProcessException">
> > >           <wsdl:part element="impl:fault" name="fault"/>
> > >   </wsdl:message>
> > >   <wsdl:message name="processTXLifeResponse">
> > >           <wsdl:part element="impl:processTXLifeReturn"
> > > name="processTXLifeReturn"/>
> > >   </wsdl:message>
> > >   <wsdl:message name="processTXLifeRequest">
> > >           <wsdl:part element="impl:processTXLife" name="part"/>
> > >   </wsdl:message>
> > >   <wsdl:portType name="TXLifeProcessorService">
> > >           <wsdl:operation name="impl:processTXLife">
> > >                   <wsdl:input message="impl:processTXLifeRequest"
> > > name="processTXLifeRequest"/>
> > >                   <wsdl:output message="impl:processTXLifeResponse"
> > > name="processTXLifeResponse"/>
> > >                   <wsdl:fault message="impl:ProcessException"
> > > name="ProcessException"/>
> > >           </wsdl:operation>
> > >   </wsdl:portType>
> > >   <wsdl:binding name="TXLifeProcessorServiceSoapBinding"
> > > type="impl:TXLifeProcessorService">
> > >           <wsdlsoap:binding style="document"
> > > transport="http://schemas.xmlsoap.org/soap/http"/>
> > >           <wsdl:operation name="impl:processTXLife">
> > >                   <wsdlsoap:operation soapAction=""/>
> > >                   <wsdl:input name="processTXLifeRequest">
> > >                           <wsdlsoap:body
> > > namespace="http://localhost:8080/axis/services/TXLifeProcessorService";
> > > use="literal"/>
> > >                   </wsdl:input>
> > >                   <wsdl:output name="processTXLifeResponse">
> > >                           <wsdlsoap:body
> > > namespace="http://localhost:8080/axis/services/TXLifeProcessorService";
> > > use="literal"/>
> > >                   </wsdl:output>
> > >                   <wsdl:fault name="ProcessException">
> > >                           <wsdlsoap:fault use="literal"/>
> > >                   </wsdl:fault>
> > >           </wsdl:operation>
> > >   </wsdl:binding>
> > >   <wsdl:service name="TXLifeProcessorServiceService">
> > >           <wsdl:port binding="impl:TXLifeProcessorServiceSoapBinding"
> > > name="TXLifeProcessorService">
> > >                   <wsdlsoap:address
> > >
> location="http://localhost:8080/axis/services/TXLifeProcessorService"/>
> > >           </wsdl:port>
> > >   </wsdl:service>
> > > </wsdl:definitions>
> > >
> > > Jim Brain, [EMAIL PROTECTED]
> > > "Researching tomorrow's decisions today."
> > > (319) 369-2070 (work)
> > > SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS
> > >
> > >
> >
>

Reply via email to