RE: [flexcoders] Signaling errors in POJO

[Peter Farland]

I think throwing an exception is ok – in Flex 2 this should be handled better where by we now use bean-rules to serialize Throwable instances (including read only properties) and return root cause chains too. The client will always receive an mx.rpc.events.FaultEvent which always has an mx.rpc.Fault instance that will contain the high level message information from your exception, but the rootCause will be the serialized bean info of your throwable type (and technically you could even create ActionScript types mapped to the Java throwable types using [RemoteClass(alias=”xyz”)]).               From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Mike_Robinson_98 Sent: Thursday, June 29, 2006 3:53 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Signaling errors in POJO   When calling a POJO method what is the preferred way to signal the RemotingService that an error condition has occurred? This error may not necessarily throw an exception in the POJO (maybe it just did not find any results). And how you include in that signal specific information about the error that could be returned to the user? Thanks, Mike __._,_.___ -- 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 Web site design development Computer software development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___