JBoss EAP 6.1.1 does not place custom exception properties in WSDL properly

Issue

• Some of the custom exception properties gets eaten up when wsdl is generated by CXF for EAP6.
• Sun metro stack of webservice is able to successfully generated the properties while CXF did not.
• Following is the custom WebService Exception class:

package exceptions;
public class BasicStructException extends Exception 
  {
     private String message;
     private String code;
     public BasicStructException(String message)
      {
         super(message);
      }
     public String getCode() {
       return code;
     }
     public void setCode(String code) {
       this.code=code;
     }
     public String toString() 
     {
       return message;
     }
  }

• After deploying the above custom exception based webservice application to EAP6 the CXF generated WSDL has the following complex type definition, (Which has missing message property):

   <xs:element name="BasicStructException" type="tns:BasicStructException"/>
   <xs:complexType name="BasicStructException">
       <xs:sequence>
           <xs:element name="code" nillable="true" type="xs:string"/>
           <xs:element name="message" nillable="true" type="xs:string"/>
       </xs:sequence>
   </xs:complexType>