Update of /cvsroot/jaxme/JaxMe2/docs
In directory sc8-pr-cvs1:/tmp/cvs-serv6918
Modified Files:
ToDo.html
Log Message:
Updated for JaxMe 2
Index: ToDo.html
===================================================================
RCS file: /cvsroot/jaxme/JaxMe2/docs/ToDo.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ToDo.html 10 Feb 2003 21:07:48 -0000 1.4
+++ ToDo.html 15 Feb 2003 22:28:10 -0000 1.5
@@ -1,118 +1,128 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>ToDo</title>
- <style type="text/css">@import url("style.css")</style>
-</head>
-<body>
-<h1>ToDo</h1>
-<p>This document describes the future of JaxMe 2. It consists of two
-parts. The more important part describes the known differences between
-JaxMe 2 and the JAXB specification. As JaxMe aims to be a JAXB
-implementation, these differences are mandatory. In other words,
-anything mentioned in this part will be implemented as soon as
-possible with high priority.</p>
-<p>The second part describes plans for JaxMe 2, which aren't governed
-by JAXB. Most of these plans have already been implemented in JaxMe 1,
-so it is very likely, that these will be realized by porting them.
-However, there is no warranty, that these features are actually
-being implemented.</p>
-<h2>Differences between JaxMe and JAXB</h2>
-<p>This section notes the known differences between JaxMe and JAXB.
-The section is incomplete: If you are used to work with JAXB, you
-will almost definitely find additional differences. We ask you to
-let the JaxMe developers know by sending an email to the mailing
-list <a href="mailto:[EMAIL PROTECTED]";>
[EMAIL PROTECTED]</a>.</p>
-<p>However, we believe that the changes required to match the
-specification will be upwards compatible.</p>
-<table border="1">
- <colgroup align="left" valign="top"></colgroup>
- <thead>
- <tr>
- <th>Missing feature or bug</th>
- <th>Description</th>
- <th>Reference</th>
- <th>Priority</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <th valign="top">Global bindings</th>
- <td valign="top" align="left">
- Support for the following attributes in globalBindings:
- collectionType, fixedAttributeAsConstantProperty,
- generateIsSetMethod, enableFailFastCheck, choiceContentProperty,
- underscoreBinding, enableJavaNamingConventions, bindingStyle</td>
- <td>6.5</td>
- <td>High</td>
- </tr
- <tr>
- <th valign="top">Schema bindings</th>
- <td valign="top" align="left">
- Support for the nameXmlTransform element in schemaBindings</td>
- <td>6.6</td>
- <td>High</td>
- </tr>
- <tr>
- <th valign="top">Property bindings</th>
- <td valign="top" align="left">Support for the following attributes
- in jaxb:property: collectionType, fixedAttributeAsConstantProperty,
- generateIsSetMethod,enableFailFastCheck</td>
- <td>6.8.1</td>
- <td>High</td>
- </tr>
- <tr>
- <th valign="top">JavaType</th>
- <td valign="top" align="left">Support for jaxb:javatype</td>
- <td>6.9</td>
- <td>High</td>
- </tr>
- <tr>
- <th valign="top">Forward references</th>
- <td valign="top" align="left">The current version of JaxMe 2 doesn't
- support forward references. In other words, a declaration like
- <code><element name="foo" type="fooType"/> only works,
- if the <code>fooType</code> declaration is located above the
- <code>foo</code> declaration.</td>
- <td>XML Schema Specification</td>
- <td>High</td>
- </tr>
- <tr>
- <th valign="top">External binding</th>
- <td>The JAXB specification mentions two different possibilities
- of customizing the schema: First of all, you may use the
- original XML schema by adding JAXB specific tags. This possibility
- has the obvious advantage, that you have anything combined in one
- file.<br>
- However, JAXB also requests the possibility to customize the
- schema bindings in an external file with a different format.
- The disadvantage is that you need two files, but you may use
- unmodified XML schema files, if they are obtained from an
- external source.<br>
- This second possibility is currently missing in JaxMe 2.</td>
- <td valign="top">6.1.3</td>
- <td valign="top">Medium; it is more important to complete the internal
binding</td>
- </tr>
- <tr>
- <th valign="top">Local Element</th>
- <td>The JAXB specification requests that a jaxb:class element may
- be specified in an element reference, overriding the settings
- in a type definition. This is not yet implemented.</td>
- <td>6.7.3.5</td>
- <td>Medium</td>
- </tr>
- <tr>
- <th valign="top">Persistence layer</th>
- <td>API for a persistence layer and bindings for a relational
- mapping, for example as present in JaxMe 1.</td>
- <td>None</td>
- <td>High</td>
- </tr>
- </tbody>
-</table>
-<a href="ChangeLog.html">NEXT</a>
-<a href="JAXB.html">PREVIOUS</a>
-<a href="index.html">TABLE OF CONTENTS</a></blockquote>
-</body></html>
+<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+
+ <meta http-equiv="Content-Type"
+ content="text/html; charset=iso-8859-1">
+ <title>The future of JaxMe: How JaxMe differs from JAXB</title>
+
+ <style type="text/css">@import url("style.css")</style>
+</head>
+ <body>
+
+<h1>The future of JaxMe: How JaxMe differs from JAXB</h1>
+
+<p>This document describes the future of JaxMe 2. It consists of two parts.
+ The more important part describes the known differences between JaxMe 2 and
+ the JAXB specification. As JaxMe aims to be a JAXB implementation, these
+differences are mandatory. In other words, anything mentioned in this part
+will be implemented as soon as possible with high priority.</p>
+
+<p>The second part describes plans for JaxMe 2 that aren't governed by JAXB.
+ Most of these plans have already been implemented in JaxMe 1, so it is very
+ likely that these changes will be realized when they are ported. However,
+ there is no guarantee that these features will be implemented in JaxMe
+ 2.</p>
+
+<h2>Differences between JaxMe and JAXB</h2>
+
+<p>This section notes the known differences between JaxMe and JAXB. The section
+ is incomplete: If you are used to work with JAXB, you will almost definitely
+ find additional differences. We ask you to let the JaxMe developers know
+by sending an email to the mailing list <a
+ href="mailto:[EMAIL PROTECTED]";>
[EMAIL PROTECTED]</a>.</p>
+
+<p>However, we believe that the changes required to match the specification
+ will be upwards compatible.</p>
+
+<table border="1">
+ <colgroup align="left" valign="top"></colgroup> <thead> <tr>
+ <th>Missing feature or bug</th>
+ <th>Description</th>
+ <th>Reference</th>
+ <th>Priority</th>
+ </tr>
+ </thead> <tbody>
+ <tr>
+ <th valign="top">Global bindings</th>
+ <td valign="top" align="left"> Support for the following
+ attributes in globalBindings: collectionType,
+fixedAttributeAsConstantProperty,
+ generateIsSetMethod, enableFailFastCheck, choiceContentProperty,
+ underscoreBinding, enableJavaNamingConventions, bindingStyle</td>
+ <td>6.5</td>
+ <td>High</td>
+ </tr>
+ <tr>
+ <th valign="top">Schema bindings</th>
+ <td valign="top" align="left"> Support for the nameXmlTransform
+ element in schemaBindings</td>
+ <td>6.6</td>
+ <td>High</td>
+ </tr>
+ <tr>
+ <th valign="top">Property bindings</th>
+ <td valign="top" align="left">Support for the following attributes
+ in jaxb:property: collectionType, fixedAttributeAsConstantProperty,
+ generateIsSetMethod,enableFailFastCheck</td>
+ <td>6.8.1</td>
+ <td>High</td>
+ </tr>
+ <tr>
+ <th valign="top">JavaType</th>
+ <td valign="top" align="left">Support for jaxb:javatype</td>
+ <td>6.9</td>
+ <td>High</td>
+ </tr>
+ <tr>
+ <th valign="top">Forward references</th>
+ <td valign="top" align="left">The current version of JaxMe 2 doesn't
+ support forward references. In other words, a declaration like
+ <code><element name="foo" type="fooType"/> only works,
+ if the <code>fooType</code> declaration is located above the
+ <code>foo</code> declaration.</code></td>
+ <td>XML Schema Specification</td>
+ <td>High</td>
+ </tr>
+ <tr>
+ <th valign="top">External binding</th>
+ <td>The JAXB specification mentions two different possibilities
+ of customizing the schema: First of all, you may use the original
+ XML schema by adding JAXB specific tags. This possibility has the
+ obvious advantage, that you have anything combined in one file.<br>
+ However, JAXB also requests the possibility to customize the
+ schema bindings in an external file with a different format.
+ The disadvantage is that you need two files, but you may use
+unmodified XML schema files, if they are obtained from an external
+source.<br>
+ This second possibility is currently missing in JaxMe 2.</td>
+ <td valign="top">6.1.3</td>
+ <td valign="top">Medium; it is more important to complete the internal
+ binding</td>
+ </tr>
+ <tr>
+ <th valign="top">Local Element</th>
+ <td>The JAXB specification requests that a jaxb:class element may
+ be specified in an element reference, overriding the settings
+ in a type definition. This is not yet implemented.</td>
+ <td>6.7.3.5</td>
+ <td>Medium</td>
+ </tr>
+ <tr>
+ <th valign="top">Persistence layer</th>
+ <td>API for a persistence layer and bindings for a relational
+ mapping, for example as present in JaxMe 1.</td>
+ <td>None</td>
+ <td>High</td>
+ </tr>
+
+ </tbody>
+</table>
+ <a href="ChangeLog.html">NEXT</a> <a
+ href="Design.html"> </a><a href="Design.html">PREVIOUS</a><a
+ href="Design.html"> </a> <a href="index.html">TABLE
+OF CONTENTS</a> <br>
+ <br>
+ <br>
+
+</body>
+</html>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jaxme-jaxb-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxme-jaxb-dev
