subject:"\[flexcoders\] Handling status event types with Remoting\/CFCs"

RE: [flexcoders] Handling "status" event types with Remoting/CFCs

2005-04-28 Thread Tim Blair

Dirk, > that's strange - "SERVER.PROCESSING" messages should > definitely trigger your fault handler. Basically, they are > just Exceptions caught by the Remoting gateway. That's what I thought. Anyway, I've worked out what was wrong -- sport the deliberate (?!) mistake: MXML: AS: call.faul

RE: [flexcoders] Handling "status" event types with Remoting/CFCs

2005-04-28 Thread Dirk Eismann

half Of Tim Blair > Sent: Thursday, April 28, 2005 1:35 PM > To: FlexCoders > Subject: [flexcoders] Handling "status" event types with Remoting/CFCs > > > Afternoon, > > I have a number of CFCs which I'm accessing through > RemoteObject calls. > I'

[flexcoders] Handling "status" event types with Remoting/CFCs

2005-04-28 Thread Tim Blair

Afternoon, I have a number of CFCs which I'm accessing through RemoteObject calls. I've noticed that if CodlFusion throws an error (built-in or custom) then the reponse comes back with an event type of "Status", which isn't handled by either the result or fault handlers specified for the callback.