XML and Objects
Bill la Forge
b.laforge at jxml.com
Tue Sep 29 18:27:00 BST 1998
>The second example above is ``internal'', the serialization uses
>class-specific elements, where class and member information are
>represented as XML elements. Internal serialization is generally done
>according to the class definition (reflection or IDL), and often
>requires a stub or class-specific behavior. Coins (if I understand
>correctly) is an example of the ``internal'' form.
I think there is a third possibility, where the objects in the DOM tree
are wrappers for application objects. These wrapper objects, then,
are responsible for connecting the data held by the DOM with the
processing capabilities of the application objects.
The wrappers serve as the glue that lets us preserve the reusability
of application components, allows them an independent inheritance,
and maintains their independence from the XML markup.
Creation of such wrappers could be driven by the XSchema for the
markup language and reflection on the application classes, but should
accept input to support non-obvious mappings.
This is what I'm trying to drive towards with coins.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev