If Im not mistaken ..This is an Adobe question so consulting the Adobe doc I
see the onFault excepion handler
http://livedocs.adobe.com/flash/mx2004/main_7_2/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Flash_MX_2004&file=00002990.html
e.g.
myPendingCallObj = myWebService.methodName(params)
myPendingCallObj.onFault = function(fault)
{
// catch the SOAP fault
DebugOutputField.text = fault.faultstring;
// add code to handle any faults, for example, by telling the
// user that the server isn't available or to contact technical
// support
}
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Eran Chinthaka" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, May 23, 2007 1:51 PM
Subject: Re: [Axis2] Getting rid of HTTP 500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeremy Smith wrote:
I am trying to use Flash to connect to an axis2 service. Works OK.
But, unfortunately flash is a little bit slow in the head, and when a
(deliberate) exception is thrown in the service to create a fault, flash
sees the HTTP/500 error and only gives the error "Unable to connect to
URL". In other words, because of that status code, I can't get any
useful fault information inside of flash. I have read that if you just
send HTTP/200 OK (even though that is against the SOAP spec) that flash
will be able to cope and the exception handling will work properly.
So the question is: is there any way I can tell axis (on Tomcat 5.5) to
send HTTP/200 even on a fault?
I see this same as building web browsers to render wrong or malformed
htmls :). Anyway, I don't think you have a way to do this inside Axis2,
unless you go and look in to the code.
If you are desperate I can tell exactly where to change. Then you have
to compile the code and use it (the open-source way.). If we do not
wanna look at our ugly code, Roberts's suggestion will also work just
fine.
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGVH8TjON2uBzUhh8RAih8AJ4/ylNqSO7aYgeRImFYh5FGrOY4vACfeTwp
0CCXLQFHIoF1Rs2feer+rHU=
=D5H3
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
