Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-4383

Unexpected subelement applicationID - from Stub's parse method

Rank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 1.4.1
    • 1.6.0
    • adb, client-api, ide plugins, wsdl
    • None
    • Tomcat 5.5, Axis2 1.4.1, Eclipse 3.4.2, Axis2 Code generator plugin

    Description

      Hello,
      I am stuck with the "Unexcpected subelement applicationID" ADBException in my Client stub.
      I used Eclipse code generator plugin to generate the client code for my wsdl.
      I created a wrapper client which calls the stub class, has a hard coded input soap xml and calls the Stub's parse method with an XMLStreamReader.
      My input xml is:
      <?xml version='1.0' encoding='utf-8'?>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:ns1="http://service.wellsfargo.com/entity/message/2007"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:ns3="http://service.wellsfargo.com/provider/System2/bntService/getBankerNotes/2007/"
      xmlns:ns2="http://service.wellsfargo.com/entity/message/2007/">
      <soapenv:Header/>
      <soapenv:Body>
      <ns3:getBankerNotes>
      <applicationID>20091133500003</applicationID>
      <requestorLoc>02604</requestorLoc>
      <requestorID>NWCB0090</requestorID>
      </ns3:getBankerNotes>
      </soapenv:Body>
      </soapenv:Envelope>

      I debugged through the parse method and the point where the exception is thrown is:

      if (reader.isStartElement() && new javax.xml.namespace.QName("","requestorLoc").equals(reader.getName())){

      since reader.getName() is still stuck at "applicationID" whereas the flow has gone to "requestorLoc"
      It seems like reader.next() is actually not moving the pointer or something.
      Your quick reply and help with this is highly appreciated!!
      -wsnewbie

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            veithen Andreas Veithen
            wsnewbie Ramya
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 25m
                25m
                Remaining:
                Remaining Estimate - 25m
                25m
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment