[
Lists Home |
Date Index |
Thread Index
]
Dare - Thanks for pointing that out. To clarify, the point is that the BEA
XMLBeans architectural approach does allow for 100% compliance with W3C XML
Schema. As the current release is an early beta, it doesn't yet support the
items listed in secution 3U of the FAQ, but it will do so in later
releases...
Thanks,
Samir
-----Original Message-----
From: Dare Obasanjo [mailto:dareo@microsoft.com]
Sent: Wednesday, February 12, 2003 3:09 PM
To: Samir Kothari; xml-dev@lists.xml.org
Subject: RE: [xml-dev] New tool for handling XML in Java
> -----Original Message-----
> From: Samir Kothari [mailto:skothari@bea.com]
> Sent: Wednesday, February 12, 2003 2:52 PM
> To: xml-dev@lists.xml.org
>
> Here's a little info on how it works: in cases where a schema
> definition is available, XMLBeans provides a set of Java
> classes to offer strongly-typed Java access to underlying XML
> data. Importantly, XMLBeans will support 100% of schema.
Are you saying that XMLBeans can represent all the datatypes, structures
and constraints of W3C XML Schema in Java? This seems to conflict with
the FAQ where it states
u. What portions of XML Schema are not supported in the beta release?
The current release of the XMLBeans service does not support:
* Includes, although imports are supported
* Redefine
* Substitution groups
* Key / keyRef / unique constraints
which seems to be a similar list to the section of W3C XML Schema not
supported by XML Serialization in the .NET Framework[0]
[0]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnexxml
/html/xml01202003.asp
--
PITHY WORDS OF WISDOM
Computers are unreliable, but humans are even more unreliable. Any
system which depends on human reliability is unreliable.
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
