tag:blogger.com,1999:blog-13546516.post1233581757466866823..comments2023-09-13T06:43:16.249-05:00Comments on Dan McCreary's Blog: XRX and MDADan McCrearyhttp://www.blogger.com/profile/12453673235365396446noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-13546516.post-23502777114626021922008-01-07T18:53:00.000-06:002008-01-07T18:53:00.000-06:00I can't agree more. We have done a number of proje...I can't agree more. We have done a number of projects with <A HREF="http://www.orbeon.com/" REL="nofollow">our implementation of XForms</A> for clients. In some cases we get to use an XML database, in others we need to use a relational database because of some constraint. And like you say, implementations that use an XML database are easier to build and maintain, because they avoid a layer of translation.<BR/><BR/>Avoiding a translation is a good thing. That may seem trivial, and it certainly is when you are used to XForms. But those who are not used to XForms might miss how important this is, as they are used to this translation layer. When you build applications with, say, a Java framework, the translation layer is a fact of life. You marvel when that translation layer doesn't make things too painful (e.g. Hibernate), but don't easily realize that you could do entirely without it with XForms/XRX.<BR/><BR/>In my mind, this is especially important when building applications with complex forms, applications where users can view and edit complex data structure. Those are cases where XForms really shines.Alessandro Vernethttps://www.blogger.com/profile/06085176014230803685noreply@blogger.com