[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-cvs
Subject:    =?iso-8859-1?q?=5BApache_XMLBeans_Wiki=5D_Updated=3A__V2Features?=
From:       xmlbeans-cvs () xml ! apache ! org
Date:       2004-07-15 21:47:57
Message-ID: 20040715214757.6909.93103 () minotaur ! apache ! org
[Download RAW message or body]

   Date: 2004-07-15T14:47:57
   Editor: DaveRemy <david.remy@bea.com>
   Wiki: Apache XMLBeans Wiki
   Page: V2Features
   URL: http://wiki.apache.org/xmlbeans/V2Features

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -8,7 +8,7 @@
 
 === Specific V2 Objectives ===
 
- * '''DOM Level II Support''' - In Version 1 the only way to get a DOM Node for an \
{{{XmlObject}}} or {{{XmlCursor}}} was to use the {{{newDOMNode}}} API which copied \
from the XML Store into a new DOM Node.  This is a fairly innefficient operation and \
the DOM Node was disconnected from the underlying XML Store so changes to the DOM \
Node were not reflected into the XML Store.  There have been a significant number of \
requests for XMLBeans to support DOM natively since lots of tools (and developers) \
know how to work with DOM already and do not know how to work with XmlCursor.  Also, \
SAAJ 1.2 now relies on an underlying DOM and having a \
[http://java.sun.com/xml/saaj/index.jsp SAAJ] implementation on XMLBeans should be \
possible (since SAAJ represents a non-lossy SOAP Envelope Document).  In Version 2 \
DOM will be implemented natively, meaning the tree within the XML Store will be able \
to represent DOM objects.  Note that XmlCursor will remain fully supported so users \
will be able to switch between DOM, {{{XmlCursor}}}, and {{{XmlObject}}} (either \
untyped or typed).   + * '''DOM Level II Support''' - In Version 1 the only way to \
get a DOM Node for an {{{XmlObject}}} or {{{XmlCursor}}} was to use the \
{{{newDOMNode}}} API which copied from the XML Store into a new DOM Node.  This is a \
fairly innefficient operation and the DOM Node was disconnected from the underlying \
XML Store so changes to the DOM Node were not reflected into the XML Store.  There \
have been a significant number of requests for XMLBeans to support DOM natively since \
lots of tools (and developers) know how to work with DOM already and do not know how \
to work with {{{XmlCursor}}}.  Also, SAAJ 1.2 now relies on an underlying DOM and \
having a [http://java.sun.com/xml/saaj/index.jsp SAAJ] implementation on XMLBeans \
should be possible (since SAAJ represents a non-lossy SOAP Envelope Document).  In \
Version 2 DOM will be implemented natively, meaning the tree within the XML Store \
will be able to represent DOM objects.  Note that {{{XmlCursor}}} will remain fully \
supported so users will be able to switch between DOM, {{{XmlCursor}}}, and \
{{{XmlObject}}} (either untyped or typed).    
  * '''Extensions''' -  In general XMLBeans generated interfaces have been pretty \
static, in large part due to the XMLBeans overall objective to correctly support the \
XML Schema type system (including the custome types defined in the schema) in Java.  \
You can map target namespace/package and element/property names but that was about \
it.  In Version 2 (this may be ported to Version 1 as well) you will be able to add \
custom functionality to generated XMLBeans interfaces/classes.  To accomplish this \
you will be able to pass the Schema Compiler two things 1) an interface that defines \
the set of methods to implement and 2) a static handler which implements this \
functionality (it is debatable whether this should be static or instance based, there \
are arguments both ways).  The underlying XMLBeans generated classes will implement \
the interface and for each method call out to the static handler.  Note that this \
capability allows XMLBeans classes to ''be'' your interface, this could allow certain \
binding type strategies to sit on top of XMLBeans.  For example, you could imagine an \
SDO ([http://dev2dev.bea.com/technologies/commonj/sdo/index.jsp Service Data \
Objects]) implementation on top of XMLBeans such that the SDO {{{DataObject}}} \
interface could be implemented by corresponding XMLBean(s).  ''7/14/04 - Note this \
feature has been implemented see this wiki page \
http://wiki.apache.org/xmlbeans/ExtensionInterfacesFeature for more information''.  

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


[prev in list] [next in list] [prev in thread] [next in thread]