History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XFIRE-667
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dan Diephouse
Reporter: Ryan Heaton
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XFire

JAXWS WebFaultHandler requires an explicit FaultInfo bean

Created: 25/Sep/06 12:15 PM   Updated: 19/Dec/06 08:52 AM
Component/s: JAX-WS
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Time Tracking:
Not Specified


 Description  « Hide
The org.codehaus.xfire.jaxws.handler.WebFaultHandler throws an exception if an explicit FaultInfo bean is not specified (with the getFaultInfo method). The spec says that if an explicit FaultInfo bean is not set, the exception class itself defines in implicit FaultInfo bean, with the cause, localizedMessage, stackTrace, and class properties excluded (see section 3.7)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dan Diephouse - 25/Sep/06 02:56 PM
Thanks Ryan. This should be pretty easy to fix. Scheduling for 1.2.2

Dan Diephouse - 30/Sep/06 09:11 PM
Thanks - I've fixed this in SVN.

Per Salomonsson - 19/Dec/06 08:52 AM
I have the exact same problem. Is there a workaround for this with XFire 1.2.1? (we cannot upgrade to 1.2.2 at the moment).

stracktrace we get:

java.lang.NullPointerException
at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireServletController.java:287)
at org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:130)
at org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
11:06:20 ERROR DefaultFaultHandler.java:35 - Fault occurred!