I downloaded jbossws-3.0.1-native-2.0.4.GA-src and modified src/main/java/org/jboss/ws/core/soap/SOAPFaultElementImpl.java and src/main/java/org/jboss/ws/core/soap/SOAPFaultImpl.java adding an "implements java.io.Serializable" to their class definition. This helped me to avoid the NotSerializableException.
In the scenario the problem problem occurred, there are three apps involved. The MS Axapta system as the WS-provider. An EAR / EJB3 app as the WS-consumer. And an standalone java app as the driver of this (unit test) calling the EJB3 session beans via their remote interface. The WS provider gets an exception and send this to WS consumer using a SOAPFault. The WS consumer does not catch the exception, so it has to be transferred to the client. And as this is a remote client the SOAPFault has to serialized. And there the Exception occurred while trying to send the SOAPFault from JBoss-Server to the standalone client app using serialization. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237086#4237086 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237086 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
