The Use of the e4x xml format might be useful, since nodes and attributed can be referenced by name. When a HTTPService makes a connection and received a result that specified to be resultFormat="e4x" you can reference any node in the xml as if it were an object. If this isn't what you're after, I would consider building yourself an InformationObjectFactory. It could exist as a singleton, with the range of InformatioObject's registered on the class for lookups. When you receive XML, call: InformationObjectFactory.instance().getObjectFromXML(myXMLString); Of course, your getObjectFromXML would need to inspect the XML to determine the object type to return, and instantiate one of these objects, populate and return it. InformationObject refers just to an object that holds instance data, like a JavaBean. The Factory should be a singleton, and provider a method to register a Class type with an associates string: registerClass(Person, "Person"); I hope this helps somewhat. Regards, Graham Weldon Suzy Lawson wrote: Sorry, for clarification, I'm very familar with the Cairngorm -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
|
- Re: [flexcoders] Re: xml framework Graham Weldon
- Re: [flexcoders] Re: xml framework Xavi Beumala
- [flexcoders] Re: xml framework Suzy Lawson
- Re: [flexcoders] Re: xml framework Michael Schmalle
- Re: [flexcoders] Re: xml framework Evert | Collab