• To: xml-dev <xml-dev@l...>
• Subject: Re: XML Object Serialization
• From: "Anthony B. Coates" <abcoates@T...>
• Date: Tue, 29 Oct 2002 20:06:28 GMT
• In-reply-to: <D60D8F448216D611A21A00508B62B5BC5DFF@e...>
• References: <D60D8F448216D611A21A00508B62B5BC5DFF@e...>
• Reply-to: "Anthony B. Coates" <abcoates@T...>

** Reply to message from Jeff Lowery <jlowery@s...> on Tue, 29 Oct
2002 11:06:00 -0800


> > 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.  
> 
> That's a design failure, not a problem due to code generation.  Any data
> model is likely to change, whether it's hand-crufted (er, crafted) data
> objects or auto-generated data objects.

Of course it is a design failure, and no-one said that it was due to the use of
code generation.  It is, of course, due to the *misuse* of code generation.

	Cheers,
		Tony.
====
Anthony B. Coates, Information & Software Architect
mailto:abcoates@T...
MDDL Editor (Market Data Definition Language)
http://www.mddl.org/

• References:
  • RE: XML Object Serialization
    • From: Jeff Lowery <jlowery@s...>

• Prev by Date: Re: Documenting XSLT (Was: Note from the Troll)
• Next by Date: Re: Documenting XSLT
• Previous by thread: RE: XML Object Serialization
• Next by thread: Re: XML Object Serialization
• Index(es):
  • Date
  • Thread