cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Shaw (JIRA)" <>
Subject [jira] Created: (CXF-784) Interceptor not setting the fault chain for HTTP Binding
Date Thu, 12 Jul 2007 15:51:05 GMT
Interceptor not setting the fault chain for HTTP Binding

                 Key: CXF-784
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.0
         Environment: WIndows XP. Tomcat 5.5, Java 5.0, CXF 2.0
            Reporter: Derek Shaw

Posting as requested by Dan Diephouse ---

>From Dan --

It seems this is a bug with the HTTP Binding. Can you file a JIRA issue for
this? I'll take a look and get a fix committed soon. In essence the problem
is we aren't adding an interceptor which sets the fault chain.

I have an exception configured  as.

@WebFault(name = "PlayerNotFound")
public class PlayerNotFoundFault extends Exception { }

There is also a faultInfo class.
@XmlRootElement(name = "ServiceException")
public class ServiceException { }

What I am finding is that when I call my service throught the XML interface (http://<server>/services/xml/)
I have configured ( using spring config provided below ), the XMLFault element is namespaced
to, while the faultInfo element is namespaced to my
default namespace. For XML this is ok... no errors.

In the case of JSON/Jettison I get a namespace exception and nothing is returned in the response.
The restful_http_binding example has the same issue.

Now, if I add to my outbound JSON namespace then I
do get the JSON response, but the content-type of the response is 'text/xml' and I cant seem

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message