We've not got many implementations so far, so there's not a
great deal to change, it's the fact that it's messy that I don't like,
rather than there's more work involved. Having real exceptions sent back to the
client is way more convenient than try/catch'ing everything and returning a
custom error object.
Maybe we can add some HttpHandlers that catch our web
services and change the response header, but it's a little nasty, especially
given those services may be called by other apps (like ClickOnce WinForms),
which we'd want to server the real response to.
We'll play around when we get that far, and see what works
best.
Thanks for the info!
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Carson Hager Sent: 20 June 2006 14:22 To: flexcoders@yahoogroups.com; flexcoders@yahoogroups.com Subject: RE: [flexcoders] Access SOAP fault code Sorry. I got you mixed up
with the original poster.
I'd be really surprised if you couldn't do
this in .NET more generically than that. I'd hate to see you have to change all
of your implementations. We made this very clear to Adobe that this was
not acceptable but that didn't seem to matter. It was made pretty clear to us
that the player would not be changing. Personally, I'd rather the product was
delayed in order to get this right from the beginning. Once more people who have
significant experience come to Flex, they are all going to find this as apalling
as you have. I'd hate to see Flex get a bad rap over
this.
Carson
From: flexcoders@yahoogroups.com on behalf of Daniel Tuppeny Sent: Tue 6/20/2006 9:21 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Access SOAP fault code
We're using .NET web services, no cold
fusion.
Looks like we'll have to wrap all responses in try/catch,
and return an object with an error property, and the actual data as another
property. Disgusting :-(
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Carson Hager Sent: 20 June 2006 14:11 To: flexcoders@yahoogroups.com; flexcoders@yahoogroups.com Subject: RE: [flexcoders] Access SOAP fault code Preaching to the choir.
:) Believe me...we feel the same way. From everything we have heard
from Adobe, this will not be addressed within the player within this
release.
That being said, does CF support anything
like filters in J2EE that allow you to do things like alter the contents of all
responses before they leave the server? If so, you can simply change that
HTTP status code to 200 for all CFC requests that have resulted in SOAP
faults.
Just to clarify, Adobe told us
informally that they would be coming up with various server side solutions that
would take care of this for you. You would have to check with them to see if
they are doing this for Cold Fusion.
Carson
From: flexcoders@yahoogroups.com on behalf of Daniel Tuppeny Sent: Tue 6/20/2006 9:06 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Access SOAP fault code
This sounds
pretty worrying. We're using SOAP without any server/proxy. So
we won't be able to get the SOAP exceptions at
all?
That sounds like
rather a fundamental flaw. It means we're unable to give the user any sensible
messages, because we don't have the exception type. Is this not being fixed for
the final release? :-(
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Carson
Hager
Sent: 20 June 2006 13:29 To: flexcoders@yahoogroups.com; flexcoders@yahoogroups.com Subject: RE: [flexcoders] Access SOAP fault code This is currently a
limitation in the Flash Player ( all versions ). SOAP faults require HTTP
500 to returned. When the FP sees a 500, it stops reading data from the
socket. The current workaround is to use the proxy or to use some other
mechanism to change the HTTP status code to 200 before the FP receives it.
Yes I realize that this is pretty poor and has serious limitations.
One last note, Adobe is evidently working
on something akin to the proxy that does this for you on your server. Clearly,
this won't help you when accessing web services one machines over which you have
no control.
Carson From: flexcoders@yahoogroups.com on behalf of m88e24 Sent: Tue 6/20/2006 3:58 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Access SOAP fault code Scenario: [Inbound Mail Scanned by MessageLabs] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ [Inbound Mail Scanned by MessageLabs] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ [Inbound Mail Scanned by MessageLabs] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- RE: [flexcoders] Access SOAP fault code Daniel Tuppeny
- RE: [flexcoders] Access SOAP fault code Carson Hager
- RE: [flexcoders] Access SOAP fault code Daniel Tuppeny
- RE: [flexcoders] Access SOAP fault code Carson Hager
- RE: [flexcoders] Access SOAP fault code Carson Hager
- RE: [flexcoders] Access SOAP fault code Dirk Eismann
- RE: [flexcoders] Access SOAP fault code Daniel Tuppeny
- RE: [flexcoders] Access SOAP fault code Carson Hager
- RE: [flexcoders] Access SOAP fault code Daniel Tuppeny
- RE: [flexcoders] Access SOAP fault code Daniel Tuppeny
- [flexcoders] Re: Access SOAP fault code kellyb723
- RE: [flexcoders] Re: Access SOAP fault code Carson Hager
- [flexcoders] Re: Access SOAP fault code kellyb723