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:
<mx:method name="getSlide"
result="event.call.resultHandler(event)"
fault="event.call.faulthandler(event)" />
AS:
call.faultHandler = Delegate.create(this, getSlideFault);
Yes, it's the old casing coming back to bite my in the bum
(faultHandler/faulthandler)!
Cheers anyway,
Tim.
--
-------------------------------------------------------
Badpen Tech - CF and web-tech: http://tech.badpen.com/
-------------------------------------------------------
RAWNET LTD - independent digital media agency
"We are big, we are funny and we are clever!"
New site launched at http://www.rawnet.com/
-------------------------------------------------------
This message may contain information which is legally
privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any
unauthorised disclosure, copying, distribution or use
of this information is strictly prohibited. Such
notification notwithstanding, any comments, opinions,
information or conclusions expressed in this message
are those of the originator, not of rawnet limited,
unless otherwise explicitly and independently indicated
by an authorised representative of rawnet limited.
-------------------------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
