DO NOT REPLY [Bug 11766] New: - The wsdl used by axis when a service is called is not the same as generated by java2wsdl

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11766>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11766

The wsdl used by axis when a service is called is not the same as generated by java2wsdl

           Summary: The wsdl used by axis when a service is called is not
                    the same as generated by java2wsdl
           Product: Axis
           Version: current (nightly)
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: james@usf.edu


When I try to retrieve an array of Access objects there is an error due to 
keyID not being recognized.
I had created my wsdl and wsdd file with java2wsdl, and everything there is
correct, all the AbstractCommon attributes are present. When I called
http://alina.acomp.usf.edu:8080/axis/services/LMSDBServer?WSDL there are a
couple of attributes missing, one being keyID.
So, it would appear that the on the fly generation is different than java2wsdl.

AxisFault
 faultCode: {http://xml.apache.org/axis/}Server.userException
 faultString: org.xml.sax.SAXException: Invalid element in
edu.usf.acomp.epic.lms.Access - keyID
 faultActor: null
 faultDetail: 
        stackTrace: org.xml.sax.SAXException: Invalid element in
edu.usf.acomp.epic.lms.Access - keyID
        at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:271)
        at
org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:857)