Im trying just to mimic this proxy behavior. Lets imagine is not one job, but is like RO, several jobs... <mx:Object id="obj" name="velo" age="44"> <mx:job area="IT" worktime="10" /> <mx:job area="IT" worktime="10" /> <mx:job area="IT" worktime="10" /> </mx:Object>
I'm using job as an arbitrary sample, truly, I wanna now how to mimic RemoteObject <mx:method behavior. What need I do to get something like this: <myStuff:MyObject some="thing"> <myStuff:aDynamicAttribute value="a"/> <myStuff:anotherDynamicAtribute value="2"/> </myStuff:MyObject> Or, more close to RO do this: <myStuff:MyObject some="thing"> <myStuff:method name="aDynamicAttribute" value="a"/> <myStuff:method name="anotherDynamicAttribute " value="2"/> </myStuff:MyObject> More clear now? About <mx:Job is not to a class, Im intend to create an attribute named job, without a lot of extra code, like: <mx:Object id="obj" name="velo" age="44"> <mx:job> <mx:Object area="IT" worktime="10" /> </mx:job> </mx:Object> If RemoteObject could omit the second <mx:Object some how, I wanna to omit too. =D Any Idea? How do I implement MyObject? VELO On Fri, Feb 29, 2008 at 10:07 PM, Rick Winscot <[EMAIL PROTECTED]> wrote: > > VELO - the Flex Object is a 'simple' storage type... the RemoteObject > along with the ObjectProxy are designed specifically for dynamic > object management - which include hierarchical storage. Is there any > reason that this won't work? > > <mx:Object id="foo" data="bar" type="job" area="TT" worktime="10" /> > > One thing that might be helpful is tying things down with a model to > assist you in object translation. As your data becomes more complex... > the need to gravitate towards DTO (data type object) and VO (view > object) becomes absolute. Take a look this example for starters. > > > http://blog.flexexamples.com/2007/09/19/converting-xml-to-objects-using-the-flex-httpservice-mxml-tag/ > > Rick Winscot > > > > On Fri, Feb 29, 2008 at 7:29 PM, VELO <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > I'm trying to do something like this: > > <mx:Object id="obj" name="velo" age="44"> > > <mx:job area="IT" worktime="10" /> > > </mx:Object> > > > > And always got: > > Could not resolve <mx:job> to a component implementation. > > > > I saw RemoteObject doing something like this: > > <mx:RemoteObject id="cargoService" fault="onFault(event)" > > destination="cargoService"> > > <mx:method name="asdasd" /> > > </mx:RemoteObject> > > > > But i cant understand why RemoteObject can do and Object cant do. > > I had try to implement my own object, who extends Proxy and override > > callProperty, getProperty and setProperty. > > But no success. > > > > Any can help me on this? > > > > VELO > > >