Complex types in fault messages - is this possible in WLS8.1?

Question

Hi all,
I'm writing a standard WSDL and want to return a complex type (or at least, a customised simple type) in a fault. This has been previously discussed here: http://forums.bea.com/bea/thread.jspa?threadID=600004053&tstart=15. I've given full details below, but the short story is that if a <fault> message if a complex type, then wsdl2service fails with odd errors. If on the same WSDL/schema I change the exception type to a builtin type (like xsd:string), it all works fine.
Google yields nothing, but if anyone has some pointers on how to do it or where to read, I'd be grateful.
Cheers,
-Tim West
Details:
I have a message and operation:
  <message name="AirlineException">
    <part name="AirlineException" element="tns:AirlineException"/>
  </message>
  <portType name="AirlinePort">
    <operation name="getCustomer">
      <input message="tns:getCustomerIn"/>
      <output message="tns:getCustomerOut"/>
      <fault name="AirlineException" message="tns:AirlineException"/>
    </operation>
  </portType>Where AirlineException is defined thus:
      <complexType name="AException">
        <sequence>
          <element name="message" type="string" nillable="true"/>
        </sequence>
      </complexType>
      <element name="AirlineException" type="tns:AException"/>(If I can get this to work, I will flesh out the complexType with some more information).
When I attempt to generate bindings with autotype and wsdl2service, autotype works but wsdl2service fails like this:
generate-server-binding-jar:
[autotype] Autotyping for wsdl Deploy/airline/airline-ws-server_war/WEB-INF/airline.wsdl
[wsdl2service] Generating web service from wsdl Deploy/airline/airline-ws-server_war/WEB-INF/airline.wsdl
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:13:
       package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] private org.jacksonwest.airline.binding.types.AException info;
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:15:
      package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public AirlineException(org.jacksonwest.airline.binding.types.AException t) {
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:19:
      package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public org.jacksonwest.airline.binding.types.AException getAirlineException() {
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:23:
      package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public void setAirlineException(org.jacksonwest.airline.binding.types.AException t) {
[wsdl2service] ^
[wsdl2service] 4 errors
[wsdl2service] java.io.IOException: Compiler failed executable.execNow, if I change the type of element 'AirlineException' to a built-in type like 'string', it all works fine. Also, I can use the generated 'AException' type in an <input> or <output> message - it's the combination of complexType and <fault> that causes the problem.
My service was originally document/literal, and I've since rewritten it as rpc/literal, as I've had more success with rpc than document on Java platforms. The problem exists in both WSDL styles.
I've read at http://e-docs.bea.com/wls/docs81/notes/new.html that WLS8.1 should be now able to handle complexTypes in faults, but for the life of me I can't do it!

Answer 1

I got it :)
The bizarre compile errors were being caused by the old version of the classes being present on the classpath that I supplied to wsdl2service. When I removed them (leaving only weblogic.jar and webservices.jar on the classpath), it worked fine first time.
So, my guess is that the ones on the classpath (the old ones) were taking precedence over the newly-generated ones, and these were obviously not compatible!
Cheers,
-Tim