Uploaded image for project: 'JAPI'
  1. JAPI
  2. JAPI-516

Control Axis2 generated naming to avoid dynamic naming scheme

    XMLWordPrintable

Details

    • New Feature
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 9.0.0
    • None
    • WSClient
    • None

    Description

          1. 'Incompatible Wrapper Types Java build-time error'
      • Axis2 generated client code can unexpectedly change class name in rare situations
      • It's been noticed that Axis2 generated stub code representing repeating (array) fields might utilize the following naming scheme <fieldName>_type<X>
      • ¬†Where X is a counter which is incremented for each distinct field in the service with shared name and the index assigned to a given field can fluctuate.
      • For instance in wsclient prior to 9.0.x, org/hpccsystems/ws/client/wrappers/gen/wsworkunits/Activities_type0Wrapper.java represented container of WUDetailsActivityInfoWrapper, but after 9.0.x it represents a container of WUResponseScopeWrapper instead.
      • SOLUTION: Users are asked to update their code to match the new wrapper class naming.

      Attachments

        Activity

          People

            mcmuja01 James McMullan
            rpastrana Rodrigo Pastrana
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: