Hi, Yes, JAX-WS support seems important.
David Blevins wrote: > > I would guess that any exception annotated with @ApplicationException > would be treated as if it was annotated with @WebFault. Not sure if > there are limitations that would prevent that, but it seems like the > most intuitive approach. > Not so sure. Runtime exception may not be treated as web fault even if they are annotated with @ApplicationException. My understanding is that a web fault must be a checked exception annotated with @WebFault. Other exceptions must be returned to the client as SOAPFaultException I've done a patch to take those rules into account. We can change the algorithm if necessary. I have started to change a piece of code to manage SOAP Headers. It worked only with no handler. Now, everything is more consistent and predictable (with or without handler). I will open a JIRA ASAP for each of these points and I will submit a patch. Please don't hesitate to give a feedback if it seems not clear or not sufficient for you. Previously, I migrated from CXF 2.0.4 incubator to CXF 2.0.9. A new CXF version (2.0.10) is out so I have to check if we can switch again to the last version Jean-Louis -- View this message in context: http://www.nabble.com/CXF-integration-tp21972675p22006750.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
