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

WSDL11ToAxisServiceBuilder fails to determine the MEP when wsdl bindings are defined in an imported document

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.6.3
    • Fix Version/s: 1.7.1
    • Component/s: kernel, wsdl
    • Labels:
      None

      Description

      When deploying a web service archive with 'useOriginalwsdl=true' and a wsdl which imports the bindings from another document, the WSDL11ToAxisServiceBuilder fails with "Cannot Determine the MEP" exception.
      The issue seems to be caused by wsdl4j which does not properly populate binding's port type operations, this is reported in wsdl4j jira:

      https://sourceforge.net/p/wsdl4j/bugs/39/

      Additionally, since Axis2 will do a depth-first search in imported wsdls to find the port type, it will not use the port type in the parent wsdl, but the unpopulated/undefined port type in the bindings' wsdl.

      I'm providing an 'EchoService.aar' that demonstrates the issue - please raise Axis2 log level to DEBUG to see the exception.

        Attachments

        1. axis2.patch
          43 kB
          Detelin Yordanov
        2. axis2.patch
          25 kB
          Detelin Yordanov
        3. EchoService.aar
          3 kB
          Detelin Yordanov
        4. stacktrace.txt
          3 kB
          Detelin Yordanov
        5. wsdl4j.patch
          17 kB
          Detelin Yordanov

          Activity

            People

            • Assignee:
              veithen Andreas Veithen
              Reporter:
              detyo Detelin Yordanov
            • Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: