Hi Anne,
 
thanks again for your advice.
I'll upgrade to Axis 1.3 asap.
 
Juliane.
 


From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Februar 2006 21:24
To: [email protected]
Subject: Re: AXIS error: makeTypeElement()

I suggest you upgrade to Axis 1.3. It fixes many bugs.
An upgrade to Axis 2 is a big deal -- it uses a different programming model, so you would need to rewrite a lot of code. But, if you have WSDLs for everything, you can use wsdl2code to generate most of it.
But Axis 2 is still a work in progress, so use with caution.

Anne

On 2/23/06, Harbarth, Juliane < [EMAIL PROTECTED]> wrote:
 
Hi Anne,
 
oh yes, when generating the server-side classes the naming was more concise. I could
deploy and look at the WSDL, great !!!  Next thing I'll do is generating the client side
classes.
Can you (or anybody else) give me some advise about upgrading. I am running Axis 1.2
(as I said) and since there are many bugs (as you said), shouldn't I upgrade to 1.3,
or rather to 2.something. What is the recommended strategy here, if there is one ?
 
Regards and many thanks,
Juliane.
 


From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Mittwoch, 22. Februar 2006 01:13

To: [email protected]
Subject: Re: AXIS error: makeTypeElement()

The WSDL validates and looks correct. But it could be that you're experiencing one of Axis 1.2's many bugs related to arrays.

I suggest that you define the "sheet" type as a named type (rather than as an anonymous type) and see if that makes a difference. e.g.,

   <element name="result">
    <complexType>
     <sequence>
      <element name="message" type="xsd:string"/>
      <element name="sheets">
       <complexType>
        <sequence>
         <element name="sheet" minOccurs="0" maxOccurs="unbounded"
            type="intf:sheet"/>
        </sequence>
       </complexType>
      </element>
     </sequence>
    </complexType>
   </element>
   <complexType name="sheet">
       <sequence>
            <element name="id" type="xsd:string"/>
            <element name="title" type="xsd:string"/>
       </sequence>
   </complexType>

Anne

On 2/21/06, Harbarth, Juliane <[EMAIL PROTECTED] > wrote:
 
 
Hi Anne (and others),
 
WSDL is attached.
 
Thanks & regards,
Juliane.
 


From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 21. Februar 2006 14:54
To: [email protected]
Subject: Re: AXIS error: makeTypeElement()

Please provide the entire WSDL.

On 2/21/06, Harbarth, Juliane <[EMAIL PROTECTED]> wrote:


Hi,

I am running Axis 1.2 and keep getting the following error when
deploying a service:

Fault - makeTypeElement() was told to create a type
"{http://cookbook}>>>result>sheets>sheet", with no containing element
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
"{http://cookbook}>>>result>sheets>sheet", with no containing element
faultActor:
faultNode:
faultDetail:
        { http://xml.apache.org/axis/}hostname:pcjhb

Why is this ? I provide an excerpt of the WSDL below, containing the
types definition.
I am more than willing to provide the complete WSDL if this is of any
help. Can it be
Axis does not like minOccurs="0" ?

Thanks & regards,
Juliane.


... xmlns:xsd="http://www.w3.org/2001/XMLSchema ">
<wsdl:types>
<schema elementFormDefault="qualified"
targetNamespace="http://cookbook"
         xmlns="http://www.w3.org/2001/XMLSchema ">
  <element name="composer">
   <complexType>
    <sequence>
     <element name="firstname" type="xsd:string" />
     <element name="lastname" type="xsd:string" />
    </sequence>
   </complexType>
  </element>
  <element name="result">
   <complexType>
    <sequence>
     <element name="message" type="xsd:string" />
     <element name="sheets">
      <complexType>
       <sequence>
        <element name="sheet" minOccurs="0" maxOccurs="unbounded">
         <complexType>
          <sequence>
           <element name="id" type="xsd:string" />
           <element name="title" type="xsd:string" />
          </sequence>
         </complexType>
        </element>
       </sequence>
      </complexType>
     </element>
    </sequence>
   </complexType>
  </element>
</schema>
</wsdl:types>




Reply via email to