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

Invalid wrapper tag name in request when using wrapped document/literal pattern in WSDL

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
    • Major
    • Resolution: Duplicate
    • 1.6.2, 1.6.3
    • None
    • codegen
    • JDK 1.7.0_71 x64, OS MS Windows 7 sp1 x64

    Description

      When using wrapped document/literal pattern in WSDL, requests, sent by the client, generated using WSDL2Code, can have invalid letter case in the request's wrapper tag name.

      We have a WSDL file containing an opertaion with document/literal style. This opertaion uses "wrapped" pattern, as described here: http://www.ibm.com/developerworks/library/ws-usagewsdl/index.html. The name of the operation has first capital letter.

      We generate client code from this wsdl, using WSDL2Java or axis2-wsdl2code-maven-plugin.

      When we try to use generated code to call the service, we get invalid soap request, having wrapper tag name starting from the lowercase letter (e.g., if an operation name is "GetUsers", we get a wrapper tag named "getUser").

      We have dived into the source code of axis2-codegen and have found the cause of that bug. InterfaceImplementationTemplate.xsl (from the org.apache.axis2.wsdl.template.java package) in several places uses java-styled operation name instead of original operation name from WSDL (lines 101, 361, 370, 377, 378).

      Attachments

        Issue Links

        Activity

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

          People

            Unassigned Unassigned
            aspirinspb Dmitriy Barbitov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment