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

RE: Must databinding imply tight coupling? (was Re: New tool

• To: "'Dare Obasanjo'" <dareo@m...>, Mike Champion <mc@x...>, xml-dev@l...
• Subject: RE: Must databinding imply tight coupling? (was Re: New tool for handlingXML in Java)
• From: Jeff Lowery <Jeff.Lowery@c...>
• Date: Thu, 13 Feb 2003 12:41:12 -0800

>      //!!!!ONE LINE OF CODE !!!!
>      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.  

• Prev by Date: Re: Strong versus (weak|runtime) typing
• Next by Date: RE: web services stack [data + context = information]
• Previous by thread: Picking the Standard (WAS RE: New tool for handling XML in Java)
• Next by thread: RE: Must databinding imply tight coupling? (was Re: New tool for handlingXML in Java)
• Index(es):
  • Date
  • Thread