You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Wes Devauld <we...@devauld.ca> on 2003/01/30 22:30:42 UTC
no containing element ERROR
Hello,
I have a web service which returns a large bean object. Some of the
member variables of the bean are other bean objects, the nesting goes as far
deep as five in some places. When I go to
http://localhost/axis/services/myTestService?WSDL I get an error:
makeTypeElement() was told to create a type
"{http://myspace}>ROOTObject>Child1>Child2", with no containing element
at org.apache.axis.wsdl.fromJava.Types.makeTypeElement(Types.java:1238)
at org.apache.axis.wsdl.fromJava.Types.writeTypeForPart(Types.java:327)
at org.apache.axis.wsdl.fromJava.Emitter.createTypes(Emitter.java:636)
at org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:383)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:268)
... snip ...
If I restart Tomcat I will get the error for a different element
ie:{http://myspace}>ROOTObject>Child1>Child4
I imagine this would disappear if I could get the emitter to grab the ROOT
element first, then the First Child1 and move down the chain instead of just
starting at an arbitrary point.
Is there a way to specify the order the types within the WSDL are created?
-W