[Xmlbeans Wiki] Update of "V2Features" by Bruce C

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlbeans Wiki" for change notification.

The "V2Features" page has been changed by Bruce C:
http://wiki.apache.org/xmlbeans/V2Features?action=diff&rev1=10&rev2=11

  
   * '''Schema to POJO/POJO to Schema''' - XMLBeans generated classes are ''tightly'' coupled to the corresponding XML Schema(s).  This is not necessarily a bad thing, it is what allows XMLBeans to fully support XML Schema functionality in a seamless and elegant manner.  XML Beans versioning has essentially the same issues as XML Schema versioning.  Consequently best practice with XMLBeans is to architecturally isolate XMLBeans through other layers using Data Access Object type patterns (using DAO informally here).  Essentially this involves mapping the data in the XMLBean to a value object or business object and the rest of the codebase writes against this mapped object.  Thus if the XML Schema changes it may be possible to change redo the mapping from the XMLBean to the value/business object. Currently with XMLBeans this is an exercise left up to the developer.  It may be possible for XMLBeans to provide a ''mapping object'' that could facilitate a more ''loosely coupled'' architecture like this.  This could entail a mapping file (or annotations) against an existing Java class that would allow the synchronization between the XMLBean and the corresponding class.  There is still a good amount of research to be done here.  It is possible this is more of a best practices document outlining a Data Access Object type pattern then an XMLBeans feature.
  
-  * '''Canonicalization''' - This is may be more research than committed feature.  One of the more expensive aspects of XML Signature is the [[http://www.w3.org/TR/xml-exc-c14n/|C14N]] processing.  This involves reading the target XML [[http://www.youtube.com/watch?v=DZZa8a8BP6I|Los Angeles Immigration Lawyer]] nodes from the tree and ''canonicalizing'' the XML.  It may be possible to improve this performance by supporting C14N directly in the XML Store (then again maybe not ..).
+  * '''Canonicalization''' - This is may be more research than committed feature.  One of the more expensive aspects of XML Signature is the [[http://www.w3.org/TR/xml-exc-c14n/|C14N]] processing.  This involves reading the target XML [[http://www.youtube.com/watch?v=DZZa8a8BP6I|Los Angeles Immigration Lawyer]] nodes from the tree and ''canonicalizing'' the XML.  It may be possible to improve [[http://www.perfect-look.net/hair-color/hair-color-ideas-choosing-the-right-color-to-enhance-your-looks.html|Hair color ideas]]this performance by supporting C14N directly in the XML Store (then again maybe not ..).
  
   * '''Hibernate integration''' - There have been multiple discussions around using XMLBeans with Hibernate (http://nagoya.apache.org/eyebrowse/ReadMsg?listName=xmlbeans-user@xml.apache.org&msgNo=305).  Ideally this would show up as some sort of plug-in into Hibernate that supports XMLBeans persistence effectively.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: commits-help@xmlbeans.apache.org