I am having issues consuming a web service using Axis2 (Axis1 doesn't work either). The error I get is

Got AxisFault during web service call: org.apache.axis2.databinding.ADBException: Unsupported type http://das.comcast.com/westservice/services customerAttribute

The raw output of this method is sampled below, the <CustomerAttributes> tag is repeated multiple times. I'm assuming ADB cannot map this output for some reason?

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

   <soap:Body>

      <ns1:westEivrQueryAttributesByNameResponse xmlns:ns1="http://das.comcast.com/westservice/services">

         <westEivrQueryAttributesByNameReturn xmlns:ns2="http://das.comcast.com/common/types" xmlns:ns3="http://das.comcast.com/westservice/services" xmlns:ns4="http://das.comcast.com/divrservice/services" xmlns:ns5="http://das.comcast.com/paymentservice/services" xmlns:ns6="http://das.comcast.com/serviceability/types">

            <customerAttributes>

               <customerAttribute xsi:type="ns3:customerAttribute" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                  <name>AccountNumber</name>

                  <state>RESOLVED</state>

                  <value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">...</value>

               </customerAttribute>

After some further review, I believe this to be related to the option in axis2 wsdl2java '-g'

-g                       Generates all the classes. It generates clases for both client side and server side including derived classes of the schema.

By manually creating the client using wsdl2java from command line and including the -g option, I can see that many more classes are created including the customerAttribute class which ADB was not finding. Is there a way to make the code generator include this option?

I don't see any way to tweak the OD wizard although it works similarly as the wsdl2java tool. According to the axis documentation, this g option allows you to generate server side code on top of the client code, this wsdl file seems to contain some server side specifications. Maybe try to merge some code generated by wsdl2java into OD generated code. Or the wsdl file has to change for OD to work. I can't see other way around it.