Re: axis on-the-fly wsdl generation problem

[Michael Thome]

Final followup, FYI. In the end, the problem turned out to be java2wsdl of wsdl2java of the following type of xsd fragment:  <xsd:element name="nest">    <xsd:complexType>      <xsd:sequence>        <xsd:element ref="nest" minOccurs="0" maxOccurs="unbounded"/>        <xsd:element ref="atom" minOccurs="0" maxOccurs="unbounded"/>      </xsd:sequence>    </xsd:complexType>  </xsd:element> It appears that it cannot handle the anonymous complexType when referenced by a subelement.  For instance, the approximate equivalent below is handled properly:  <xsd:complexType name="NestType">    <xsd:sequence>      <xsd:element ref="nest" minOccurs="0" maxOccurs="unbounded"/>      <xsd:element ref="atom" minOccurs="0" maxOccurs="unbounded"/>    </xsd:sequence>  </xsd:complexType>  <xsd:element name="nest" type="NestType"/> I've no idea why this change should make a difference, but ?wsdl is working again for me. Cheers,     Michael Michael Thome wrote: As an in-progress followup, the lack of a stack dump is due to java bug 4872096 (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4872096 ) which can be worked around by adding -Xint to the vm arguments. I'm currently getting (with the middle cut out): java.lang.StackOverflowError ...