Hi,
Be sure you are extending the mx.rpc.remoting.mxml.RemoteObject instead of
extending the
mx.rpc.remoting.RemoteObject.
Hope this helps,
Pedro Sena
On Fri, Jul 4, 2008 at 1:20 PM, mbhoisie <[EMAIL PROTECTED]> wrote:
> I'd like to have a custom remoteobject for specific error handling
> and logging. However, if I try to extend remoteobject:
>
> public dynamic class CustomRemoteObject extends RemoteObject
> {
> ...
> }
>
> It is completely unusable in an mxml file. If I try to declare any
> <mx:methods> inside of it, I get a "could not resolve <mx:method> to
> a component implemenation":
>
> <components:CustomRemoteObject>
> <mx:method ...> <!-- compiler error>
> </components:CustomRemoteObject>
>
> I know that <mx:method> is special-cased by the compiler because it
> doesn't have a component implementation. Is there a way to use custom
> remote objects in mxml with the mx:method tag? If not, is there a way
> to use custom remote objects in mxml and have callbacks at the method-
> level? Is remoteobject not supposed to be extended this way?
>
>
>
--
/**
* Pedro Sena
* Systems Architect
* Sun Certified Java Programmer
* Sun Certified Web Component Developer
*/
