>
> As for Cairngorm considerations, I can't comment on those but
> this list seems very capable of helping out in that regard.
>
I'll just followup Pete's (excellent) post by saying that there's
a methodology to tracking this down; I'd suggest reducing your
testing to a single *non cairngorm* application that successfully
invokes your remote object and gets some results back.
Once you have that working, you've confirmed that your backend
and frontend are talking to each other. You should then be able
to migrate your RemoteObject call into a Services.mxml file and
hook into Business Delegate/Command classes on the client.
But first things first ... just produce a simple TestService.mxml
that declares your RemoteObject, invokes it, and handles the
result, following all the advice that Pete gave.
Cheers,
Steven
--
Steven Webster
Technical Director
iteration::two
This e-mail and any associated attachments transmitted with it may contain
confidential information and must not be copied, or disclosed, or used by
anyone other than the intended recipient(s). If you are not the intended
recipient(s) please destroy this e-mail, and any copies of it, immediately.
Please also note that while software systems have been used to try to ensure
that this e-mail has been swept for viruses, iteration::two do not accept
responsibility for any damage or loss caused in respect of any viruses
transmitted by the e-mail. Please ensure your own checks are carried out
before any attachments are opened.
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/
