Interesting suggestion, but if I try that, I still get the following error:
"Could not resolve <components:method> to a component implementation." I've almost concluded that if you want to extend RemoteObject, you simply cannot use mx:method, because it's special cased in the compiler. -Mike --- In [email protected], Jeffry Houser <[EMAIL PROTECTED]> wrote: > > Try this: > > <components:CustomRemoteObject> > <components:method ...> > </components:CustomRemoteObject> > > > mbhoisie 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? > > > > > > > > ------------------------------------ > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: http://www.mail-archive.com/flexcoders% 40yahoogroups.comYahoo! Groups Links > > > > > > > > > > > > -- > Jeffry Houser > Flex, ColdFusion, AIR > AIM: Reboog711 | Phone: 1-203-379-0773 > -- > Adobe Community Expert <http://www.adobe.com/communities/experts/members/JeffryHouser.html> > My Company: <http://www.dot-com-it.com> > My Podcast: <http://www.theflexshow.com> > My Blog: <http://www.jeffryhouser.com> >
