I'm using .NET 2.0 WebService from Flex 2.0. If my web service throws
an
exception I do receive the exception message in
the
FaultEvent.fault.faultString in Flex.
- Kelly
--- In
[EMAIL PROTECTED]ups.com,
"Daniel Tuppeny" <[EMAIL PROTECTED]..> wrote:
>
> Cool, I
thought it just copied the one from IE! In any case, I guess the
>
WinForms one would be different. Thanks :-)
>
>
________________________________
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of Carson Hager
> Sent: 20 June 2006 15:01
> To:
[EMAIL PROTECTED]ups.com;
[EMAIL PROTECTED]ups.com
>
Subject: RE: [flexcoders] Access SOAP fault code
>
>
> You
can definitely do this so that only the flex app gets the affected
>
response. The FP has a unique user agent name that you can look at to
>
determine if you need to change the http status code or not. That's how
>
we've done this.
>
>
> Carson
>
>
>
________________________________
>
> From: [EMAIL PROTECTED]ups.com
on behalf of Daniel Tuppeny
> Sent: Tue 6/20/2006 9:50 AM
> To: [EMAIL PROTECTED]ups.com
>
Subject: RE: [flexcoders] Access SOAP fault code
>
>
>
> 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:
[EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of Carson Hager
> Sent: 20 June 2006 14:22
> To:
[EMAIL PROTECTED]ups.com;
[EMAIL PROTECTED]ups.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: [EMAIL PROTECTED]ups.com
on behalf of Daniel Tuppeny
> Sent: Tue 6/20/2006 9:21 AM
> To: [EMAIL PROTECTED]ups.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: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of Carson Hager
> Sent: 20 June 2006 14:11
> To:
[EMAIL PROTECTED]ups.com;
[EMAIL PROTECTED]ups.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: [EMAIL PROTECTED]ups.com
on behalf of Daniel Tuppeny
> Sent: Tue 6/20/2006 9:06 AM
> To: [EMAIL PROTECTED]ups.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: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of Carson Hager
> Sent: 20 June 2006 13:29
> To:
[EMAIL PROTECTED]ups.com;
[EMAIL PROTECTED]ups.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: [EMAIL PROTECTED]ups.com
on behalf of m88e24
> Sent: Tue 6/20/2006 3:58 AM
> To: [EMAIL PROTECTED]ups.com
>
Subject: [flexcoders] Access SOAP fault code
>
>
>
>
Scenario:
>
> Flash players talks directly to a SOAP web service,
no proxy is used.
> The proxy attribute of the WebService element is set
to "false". A
> specific web service operation generates an application
level user
> exception and the faultcode and faultstring is returned in
the SOAP
> body. The FaultEvent object received by the fault handler
function
> does not contain the faultcode and the faultstring from the
SOAP
> message. The faultDetail in the FaultEvent object is of type
"ioError"
> and the error text is "Error #2032: Stream error ........" .
Whilst the
> actual SOAP faultcode is "soapenv:Server.userException"
and the SOAP
> faultstring is
"coldfusion.xml.rpc.CFCInvocationException:
>
[coldfusion.runtime.UndefinedElementException : Element SPELER.ID
is
> undefined in SESSION."
>
> This is custom exception
thrown by a remote function in a ColdFusion
> CFC. This is not an ioError.
>
> A TCPmonitor shows the correct message request and response
with the
> faultstring and faultcode as expected.
>
> How
can the actual SOAP faultcode and faultstring be retrieved from
> the
FaultEvent or in any other way. Why is the fault description in
> the
FaultEvent object totally different from the actual SOAP fault
> message.
It is not a transport error so why does the FaultEvent shows
> an ioError.
It is an application level exception and as such returned
> to the Flash
application encapsulated in the SOAP body.
>
> Any suggestions,
thank you
>
>
>
>
> [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
>
__________________________________________________________
>
>
>
> [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
>
__________________________________________________________
>
