tag:blogger.com,1999:blog-38586079.post8325947815970948056..comments2024-01-22T15:27:00.730+08:00Comments on One size doesn't fit all: JAX-WS: Throwing generic SOAPFaults under WLS 10.3Chris Muirhttp://www.blogger.com/profile/06566648350240654621noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-38586079.post-16342444220331077942009-07-26T21:37:10.763+08:002009-07-26T21:37:10.763+08:00Hmmm, not sure Shane. I think there's a hint ...Hmmm, not sure Shane. I think there's a hint in your question though. My SOAPFault is only thrown in the JAX-WS endpoint classes I've created, not in any JAXB classes. I've also tested it using the JAX-WS Provider API. How and where are you throwing the fault?<br /><br />CM.Chris Muirhttps://www.blogger.com/profile/06566648350240654621noreply@blogger.comtag:blogger.com,1999:blog-38586079.post-81497658396321831772009-07-24T23:29:53.433+08:002009-07-24T23:29:53.433+08:00How are you able to throw a SOAPFaultException web...How are you able to throw a SOAPFaultException weblogic keeps yelling that JAXB can't handle interfaces so it can't serialize javax.xml.soap.SOAPFaultUnknownhttps://www.blogger.com/profile/08230241630060278943noreply@blogger.com