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

Incorrect stub generated when upgrading from axis2 v1.5.1 to v1.7.4

Rank to TopRank to BottomAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.7.4
    • Fix Version/s: None
    • Component/s: codegen
    • Labels:
      None

      Description

      I'm having a problem with generating the correct stub after upgrading from axis2-1.5.1 to axis2-1.7.4. The WSDL I'm working with has a service with 2 ports defined having different binding. When generating the client code, I'm only getting the stub for the second port. With axis2-1.5.1, I was getting the stub for the first port. I'm using another tool that is part of a larger product. The tool I'm using uses CodeGenerationEngine to generate the client code and is not using the command line option -pn. I know that using the command line option -pn will create the stub that is needed. The default behavior (when -pn is not specified) seems different between these axis2 version. I've tried switching the order of the port definition in the WSDL but it didn't make a difference. With axis2 1.7.4, how is the port selected if -pn option is not specified? Is it possible to apply the default behavior of 1.5.1 to 1.7.4?

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              Unassigned
              Reporter:
              dluong Diep Luong

              Dates

              • Created:
                Updated:

                Issue deployment