Comments on: Handling Web Service exception in Flex code

By: Rama

Rama — Fri, 09 Nov 2007 18:53:37 +0000

I use Axis and Flex2 and for some reason, I am unable to get it to work. Can someone post the source code for the Exception Logic on the J2EE side?

I think I might have messed up the ClientException class. Since I use Axis, should it extend Exception?

Thanks,
Rama

By: Rado

Rado — Mon, 16 Jul 2007 08:44:48 +0000

It works for me too. I am using Axis and Flex 2.0.1. I did not have to do any extra steps, and now my event.fault.faultString contains correct text (”exception name: exception.getMessage()”)

thanks for your help :-)

anyway, do you think that Flex could support the “standard” SOAP faults code 500 in the future?

By: Java Donkey

Java Donkey — Tue, 08 May 2007 15:30:15 +0000

Interesting read, thanks for the post! I didn’t know that a web service standard was to set the error code to 500.

By: Java Donkey - The Java Donkey comments on Java programming as well as other topics. » Error Handling in Servlet Filters using web.xml

Tue, 08 May 2007 15:28:05 +0000

[…] a seperate but related read, check out Handling Web Service Exceptions and XFire. This entry is filed under J2EE. You can follow any responses to this entry through the RSS 2.0 […]

By: RD

RD — Tue, 06 Mar 2007 06:33:00 +0000

It’s difficult to say without looking into the code - it works for me. I guess you already checked that: service.doSomething.addEventListener(”fault”, responder.fault); is assigned to “fault”?

By: quai83

quai83 — Thu, 01 Mar 2007 09:27:00 +0000

Hi,

It does not work in XFire too, the succeed callback is called instead of the fault callback. Although the soap message is populated with the correct exception details, but calling succeed callback leaves me no idea to handle the exception details. Any idea?

Thanks.

Best Regards,
Chee Seng

By: quai83

quai83 — Thu, 01 Mar 2007 06:55:00 +0000

Hi,

I cannot get it working with Axis, I am using Axis 1.4. I have set the HTTP status code from 500 to 200 using HttpServletResponseWrapper. However, instead of calling on the callback function for fault, Flex calls the success callback function. The soap response is a soap fault. Is it because status code 200 indicate that the invocation succeed without fault?

Thanks for any help in advance.

Best Regards,
Chee Seng