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.