[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML Object Serialization

• To: "Anthony B. Coates" <abcoates@T...>,xml-dev <xml-dev@l...>
• Subject: Re: XML Object Serialization
• From: Kal Ahmed <kal@t...>
• Date: Tue, 29 Oct 2002 21:16:51 +0000
• In-reply-to: <E186bO7-0000rO-00@FUSMTA03-LRS>
• References: <D60D8F448216D611A21A00508B62B5BC5DFD@e...> <E186bO7-0000rO-00@FUSMTA03-LRS>
• Reply-to: kal@t...
• User-agent: KMail/1.4.1

On Tuesday 29 October 2002 18:43, Anthony B. Coates wrote:
> ** Reply to message from Jeff Lowery <jlowery@s...> on Tue, 29
> Oct 2002 10:25:39 -0800
>
> > > Sure, and I've seen enormous problems come out of people
> > > "compiling" XML schemas into classes using the tools that are now
> > > available. I mean, one of the main reasons for using XML is to decouple
> > > applications, and then people compile the XML schemas into code so that
> > > they tightly couple their applications to this week's version of the
> > > XML.
> >
> > How about instead of generating classes, these code generators generated
> > interfaces + implementations? Still not perfect, but at least you're
> > coding your app to an interface.  You can then change the interface,
> > either through extension or dynamic proxies. The implementation classes
> > can also be extended, or rewritten altogether if needs be.
>
> No, no help at all.  It's not a problem that you solve by trying to use
> another Java feature.  The problem is if the auto-generated XML->Java code
> is called from all throughout the application codebase.  If the XML
> changes, everything breaks.  You need to hide the auto-generated code
> behind a facade so that almost all of the application code is unable to
> call it directly.  Then, when there are changes to the XML, the effect on
> the codebase is limited to a small, pre-determined set of classes.
>

How about coding to an abstract data model with greater expressive power than 
a simple XML schema (small s). Like a topic map or RDF abstraction for 
example ? (I'm only slightly joking here ;-)

Other folks have already said this, but the point about XML data binding is 
that your schema is the contract between the data provider and the data 
consumer. If the data provider breaks the contract or if you are working in 
an environment where such contracts are not worth the bits they are encoded 
in, then its probably true to say that XML data binding is not for you...

Cheers,

Kal
-- 
Kal Ahmed, techquila.com
XML and Topic Map Consultancy

e: kal@t...
p: +44 7968 529531
w: www.techquila.com

• References:
  • RE: XML Object Serialization
    • From: Jeff Lowery <jlowery@s...>
  • Re: XML Object Serialization
    • From: "Anthony B. Coates" <abcoates@T...>

• Prev by Date: Re: Documenting XSLT
• Next by Date: another XPointer scheme non-announcement
• Previous by thread: Re: XML Object Serialization
• Next by thread: Re: XML Object Serialization
• Index(es):
  • Date
  • Thread