Hi again, I'm fixing the exception behavior but I need to be sure.
In the EJB specification, we can receive : - ApplicationException: - checked exception declared in the method signature - runtime exception + @ApplicationException - SystemException - everything else For web service, the specification is not as clear. My understanding is: - a WebFault is a checked exception with the @WebFault annotation. The client will then receive the business checked exception. - everything else is returned to the client as a SOAPFaultException So for checked exception EJB and WS calls are equivalent but what about EJB ApplicationException based on RuntimeException + @ApplicationException ? I have some ideas to fix exception handling but I need your opinion. Regards, Jean-Louis Jean-Louis MONTEIRO wrote: > > Hi all, > > I would like to have your inputs regarding CXF integration as the default > JAX-WS provider. > To be honest, I've done some tests around JAX-WS within OpenEJB and I'm > facing problems. > > I'm looking how to enhance CXF integration. > Here are some problems: > 1. when no (SOAP or logical) handler is defined, WebFault does not work ! > 2. SOAP headers don't work when using headers > > I have found a solution for the second topic and I'm still investigating > on the first one. > > Kind regards, > Jean-Louis MONTEIRO > > > -- View this message in context: http://www.nabble.com/CXF-integration-tp21972675p21975841.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
