• To: "Anthony B. Coates" <abcoates@T...>
• Subject: Re: XML Object Serialization
• From: tblanchard@m...
• Date: Wed, 30 Oct 2002 01:31:49 +0100
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <E186bO7-0000rO-00@FUSMTA03-LRS>

On Tuesday, October 29, 2002, at 07:43  PM, Anthony B. Coates wrote:
> 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.

Of course, this is only a problem with statically typed languages like 
Java.  Dynamically typed languages cope much better.

• Follow-Ups:
  • Re: XML Object Serialization
    • From: "Anthony B. Coates" <abcoates@T...>

• References:
  • Re: XML Object Serialization
    • From: "Anthony B. Coates" <abcoates@T...>

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