Hi ,

 

My WSDL document has following faults declared:

 

</xs:element>

<xs:element name="getShreddingVisitProfileCount_fault">

<xs:complexType>

<xs:sequence>

<xs:element name="getShreddingVisitProfileCount_fault" type="xs:string">

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="getShreddingVisitProfile_fault">

<xs:complexType>

<xs:sequence>

<xs:element name="getShreddingVisitProfile_fault" type="xs:string">

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

 

I am deploying my service as an Axis2 Archive on Tomcat server. My Webservice client is a Web Sphere portal server. When I generate an Exception and try getting the fault string on the client side, I get a ClassCastException. I happen to see that the Exception class name as well as the super classes differ on the server side and the client side

This is how it is on the server side

 

public static class GetShreddingVisitProfile_faultException

        extends java.rmi.RemoteException {

        private com.ironmtn.awarews.service.shredding.GetShreddingVisitProfileFaultDocument faultMessage;

 

        public void setFaultMessage(

            com.ironmtn.awarews.service.shredding.GetShreddingVisitProfileFaultDocument msg) {

            faultMessage = msg;

        }

 

        public com.ironmtn.awarews.service.shredding.GetShreddingVisitProfileFaultDocument getFaultMessage() {

            return faultMessage;

        }

    }

 

Please let me know if  I am missing something or is It advisable to use javax.xml.soap.SOAPFaultException and how to use it in Axis2.

 

Thanks

Siva Rajamani

 

 

Reply via email to