RE: [xml-dev] Must databinding imply tight coupling? (was Re: New tool for handlingXML in Java)

["Dare Obasanjo" <dareo@microsoft.com>]

> -----Original Message-----
> From: Jeff Lowery [mailto:Jeff.Lowery@creo.com] 
> Sent: Thursday, February 13, 2003 12:41 PM
> To: Dare Obasanjo; Mike Champion; xml-dev@lists.xml.org
> 
> >      double PEratio = (double)
> >        doc.CreateNavigator().Evaluate("/*/price div 
> > (/*/revenues - /*/expenses)");     
> >  
> >      Console.WriteLine("PE Ratio = {0}", PEratio);      
> 
> This looks better, but:
> 
> 1) what if a field is mispelled?
> 2) what if an operator is undefined for the field value?
> 3) what if the cast is invalid for the value returned?
> 
> All these errors are caught at runtime, whereas in the 
> binding example, such errors occur at compile-time.  That's a 
> big, big win for data binding using schema definitions.  

This assumes data binding in a statically typed language which seems to
me to imply overly tight coupling. However given the popularity of
Object<->XML binding technologies it seems that most developers would
forego the loose coupling that many would consider a benefit of XML to
gain an easier processing model. 

-- 
PITHY WORDS OF WISDOM 
Identical units which test in an identical fashion will not behave in an
identical fashion in the field.                               

This posting is provided "AS IS" with no warranties, and confers no
rights.