The only thing I can think of off hand is that you for got to put a "fault=" in your <mx:RemoteObject> or you might have put it in as onFault
I put this in my onFault so that I can at least see what the error is on the client side while debugging: public function onFault( event : Object ) : Void { mx.controls.Alert.show(event.fault.faultstring, 'Error'); } I also took a quick look at the book and I see that on Pages 463 and 464 they are missing the fault piece. Depending on how you are coding it would look like this: fault="event.call.faultHandler( event )" or this fault="event.call.faultHandler( event.result )" -Kent -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Libby Sent: Thursday, June 09, 2005 1:08 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Question for the RIA Book Guys (or anyone with a Java back end for that matt I am very sorry, I got your name wrong. It is not Stephen, but Steven! I hate it when people misspell my name : ( --- In flexcoders@yahoogroups.com, "Libby" <[EMAIL PROTECTED]> wrote: > Hi, Stephen, et al > > I have implemented your business delegate scenario as outlined in the > book in chapter 20. It works very well, except for when java throws an > exception, the onFault never catches it. In network Monitor, I can see > that an onStatus, probably System.onStatus, is invoked. I coded my > delegate classe exactly as you have on page 479, and the onResult > works fine. Can you give me any pointers to "make" the onFault catch > the exception so I can handle it? > > Thanks, > Libby Yahoo! Groups Links
smime.p7s
Description: S/MIME cryptographic signature