You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by jo...@apache.org on 2006/01/07 00:22:27 UTC
svn commit: r366595 [1/2] - in /webservices/site/trunk/targets/jaxme: ./ js/
js/patterns/ manual/ pm/ xs/
Author: jochen
Date: Fri Jan 6 15:20:47 2006
New Revision: 366595
URL: http://svn.apache.org/viewcvs?rev=366595&view=rev
Log:
Release of JaxMe 0.5.1
Added:
webservices/site/trunk/targets/jaxme/downloads.cgi
Modified:
webservices/site/trunk/targets/jaxme/downloads.html
webservices/site/trunk/targets/jaxme/js/index.html
webservices/site/trunk/targets/jaxme/js/index.pdf
webservices/site/trunk/targets/jaxme/js/patterns/typesafeenum.html
webservices/site/trunk/targets/jaxme/mailinglists.html
webservices/site/trunk/targets/jaxme/mailinglists.pdf
webservices/site/trunk/targets/jaxme/manual/apa.html
webservices/site/trunk/targets/jaxme/manual/apb.html
webservices/site/trunk/targets/jaxme/manual/ch01.html
webservices/site/trunk/targets/jaxme/manual/ch01s02.html
webservices/site/trunk/targets/jaxme/manual/ch02.html
webservices/site/trunk/targets/jaxme/manual/ch02s02.html
webservices/site/trunk/targets/jaxme/manual/go01.html
webservices/site/trunk/targets/jaxme/manual/index.html
webservices/site/trunk/targets/jaxme/manual/pr01.html
webservices/site/trunk/targets/jaxme/news.html
webservices/site/trunk/targets/jaxme/news.pdf
webservices/site/trunk/targets/jaxme/pm/ino.html
webservices/site/trunk/targets/jaxme/pm/ino.pdf
webservices/site/trunk/targets/jaxme/release.html
webservices/site/trunk/targets/jaxme/release.pdf
webservices/site/trunk/targets/jaxme/resources.html
webservices/site/trunk/targets/jaxme/resources.pdf
webservices/site/trunk/targets/jaxme/xs/logical.html
Added: webservices/site/trunk/targets/jaxme/downloads.cgi
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/downloads.cgi?rev=366595&view=auto
==============================================================================
--- webservices/site/trunk/targets/jaxme/downloads.cgi (added)
+++ webservices/site/trunk/targets/jaxme/downloads.cgi Fri Jan 6 15:20:47 2006
@@ -0,0 +1,7 @@
+#!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+# python includes correctly)
+# Copied from Stefan's page on mirrors
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
\ No newline at end of file
Modified: webservices/site/trunk/targets/jaxme/downloads.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/downloads.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/downloads.html (original)
+++ webservices/site/trunk/targets/jaxme/downloads.html Fri Jan 6 15:20:47 2006
@@ -361,10 +361,10 @@
<ul>
-<li>ws-jaxme-0.5-bin.tar.gz: <strong>d9e3151576fee5fc4f8af907a71f9096</strong>
+<li>ws-jaxme-0.5.1-bin.tar.gz: <strong>cc571bbf47d261fb7b8ae3d5d22f70d8</strong>
</li>
-<li>ws-jaxme-0.5-src.tar.gz: <strong>59991a2ecdfada900ad836f9cc581a1e</strong>
+<li>ws-jaxme-0.5.1-src.tar.gz: <strong>673db466c6ccc9e6fb6616d0404de6d6</strong>
</li>
</ul>
Modified: webservices/site/trunk/targets/jaxme/js/index.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/js/index.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/js/index.html (original)
+++ webservices/site/trunk/targets/jaxme/js/index.html Fri Jan 6 15:20:47 2006
@@ -313,7 +313,7 @@
jar file and make JaxMe 2 based on it.</p>
<p>In a way, the JavaSource framework is still a part of JaxMe, because it lives
under the same Apache hat. The sources are located in the same
- CVS server and the distribution comes from the same file server.
+ SVN server and the distribution comes from the same file server.
The administrators and developers are typically the same. We'll see, what the
future brings.</p>
</div>
Modified: webservices/site/trunk/targets/jaxme/js/index.pdf
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/js/index.pdf?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/site/trunk/targets/jaxme/js/patterns/typesafeenum.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/js/patterns/typesafeenum.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/js/patterns/typesafeenum.html (original)
+++ webservices/site/trunk/targets/jaxme/js/patterns/typesafeenum.html Fri Jan 6 15:20:47 2006
@@ -134,67 +134,52 @@
<li>
<font color="#CFDCED">JaxMeJS</font>
<ul>
-
<li>
<a href="../index.html">Introduction</a>
</li>
-
<li>
<a href="../factory.html">The JavaSource factory</a>
</li>
-
<li>
<a href="../methods.html">Writing methods</a>
</li>
-
<li>
<a href="../placeholders.html">Placeholders</a>
</li>
-
<li>
<a href="../optimizations.html">Optimizations</a>
</li>
-
<li>
<a href="../sql.html">Writing SQL</a>
</li>
-
</ul>
</li>
<li>
<font color="#CFDCED">Patterns</font>
<ul>
-
<li>
<a href="proxy.html">Proxy Objects</a>
</li>
-
<li>
<a href="proxy.html#multiple_inheritance">Multiple Inheritance</a>
</li>
-
<li>
<span class="sel"><font color="#ffcc00">Typesafe Enumerations</font></span>
</li>
-
<li>
<a href="chains.html">Proxy chains</a>
</li>
-
<li>
<a href="versioning.html">Versioning</a>
</li>
-
</ul>
</li>
<li>
<font color="#CFDCED">Applications</font>
<ul>
-
<li>
<a href="../apps/xmlrpc.html">Apache XML-RPC Clients</a>
</li>
-
</ul>
</li>
</ul>
Modified: webservices/site/trunk/targets/jaxme/mailinglists.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/mailinglists.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/mailinglists.html (original)
+++ webservices/site/trunk/targets/jaxme/mailinglists.html Fri Jan 6 15:20:47 2006
@@ -292,7 +292,7 @@
works by sending mail to
<a href="mailto:jaxme-dev-subscribe@ws.apache.org">jaxme-dev-subscribe@ws.apache.org</a>,
or <a href="mailto:jaxme-dev-unsubscribe@ws.apache.org">jaxme-dev-unsubscribe@ws.apache.org</a>,
- respectively. This list is receiving CVS notifications.</p>
+ respectively. This list is receiving SVN notifications.</p>
<p>Searchable archives of this list can be found on
<a href="http://mail-archives.apache.org/eyebrowse/SummarizeList?listId=172">
http://mail-archives.apache.org/eyebrowse/SummarizeList?listId=172
Modified: webservices/site/trunk/targets/jaxme/mailinglists.pdf
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/mailinglists.pdf?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/site/trunk/targets/jaxme/manual/apa.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/apa.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/apa.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/apa.html Fri Jan 6 15:20:47 2006
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix 1. License</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="ch02s02.html" title="Marshalling objects"><link rel="next" href="apb.html" title="Appendix 2. FAQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Appendix 1. License</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02s02.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="apb.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 cl
ass="title"><a name="N105B7"></a>Appendix 1. License</h2></div></div><div></div></div><p>JaxMe comes to you under the terms of The Apache Software License:</p><p>Apache License</p><p>Version 2.0, January 2004</p><p><a href="http://www.apache.org/licenses/" target="_top">http://www.apache.org/licenses/</a></p><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N105C4"></a>TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION</h2></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p>Definitions.</p><p>"License" shall mean the terms and conditions for use, reproduction,
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix A. License</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="ch02s02.html" title="Marshalling objects"><link rel="next" href="apb.html" title="Appendix B. FAQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Appendix A. License</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02s02.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="apb.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 cl
ass="title"><a name="N105C4"></a>Appendix A. License</h2></div></div></div><p>JaxMe comes to you under the terms of The Apache Software License:</p><p>Apache License</p><p>Version 2.0, January 2004</p><p><a href="http://www.apache.org/licenses/" target="_top">http://www.apache.org/licenses/</a></p><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N105D1"></a>TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION</h2></div></div></div><div class="orderedlist"><ol type="1"><li><p>Definitions.</p><p>"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
</p><p>"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
@@ -142,7 +142,7 @@
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
- </li></ol></div><p>END OF TERMS AND CONDITIONS</p></div><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10602"></a>APPENDIX: How to apply the Apache License to your work.</h2></div></div><div></div></div><p>To apply the Apache License to your work, attach the following
+ </li></ol></div><p>END OF TERMS AND CONDITIONS</p></div><div class="simplesect" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1060F"></a>APPENDIX: How to apply the Apache License to your work.</h2></div></div></div><p>To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
@@ -150,7 +150,7 @@
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
- </p><div class="example"><a name="N10607"></a><p class="title"><b>Example 1.1. </b></p><p>Copyright [yyyy] [name of copyright owner]</p><p>Licensed under the Apache License, Version 2.0 (the "License");
+ </p><div class="example"><a name="N10614"></a><p class="title"><b>Example A.1. </b></p><p>Copyright [yyyy] [name of copyright owner]</p><p>Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
<a href="http://www.apache.org/licenses/LICENSE-2.0" target="_top">http://www.apache.org/licenses/LICENSE-2.0</a>
@@ -159,4 +159,4 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
- </p></div></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch02s02.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="apb.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Marshalling objects </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Appendix 2. FAQ</td></tr></table></div></body></html>
\ No newline at end of file
+ </p></div></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch02s02.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="apb.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Marshalling objects </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Appendix B. FAQ</td></tr></table></div></body></html>
\ No newline at end of file
Modified: webservices/site/trunk/targets/jaxme/manual/apb.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/apb.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/apb.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/apb.html Fri Jan 6 15:20:47 2006
@@ -1,9 +1,9 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix 2. FAQ</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="apa.html" title="Appendix 1. License"><link rel="next" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Appendix 2. FAQ</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="apa.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="
N10611"></a>Appendix 2. FAQ</h2></div></div><div></div></div><p>This section contains a list of frequently asked questions. And, of course, their answers. :-)</p><div class="qandaset"><dl><dt>2.1. <a href="apb.html#N10618">General questions</a></dt><dd><dl><dt>Q: <a href="apb.html#N1061D">What is it?</a></dt><dt>Q: <a href="apb.html#N10624">Why should I choose JaxMe and not JAXB?</a></dt><dt>Q: <a href="apb.html#N10639">Why the name "JaxMe"?</a></dt><dt>Q: <a href="apb.html#N10642">Are there any reference projects?</a></dt></dl></dd><dt>2.2. <a href="apb.html#N10651">The Generator</a></dt><dd><dl><dt>Q: <a href="apb.html#N10656">What is the supported subset of XML Schema?</a></dt><dt>Q: <a href="apb.html#N10673">What is the supported subset of JAXB?</a></dt><dt>Q: <a href="apb.html#N10681">How is the EJB support working?</a></dt><dt>Q: <a href="apb.html#N1068C">What are JaxMe's "find methods" and "list methods"?</a></dt><dt>Q: <a href="apb.html#N10697">Why are th
e field names uppercased when using the JaxMeJdbcSG?</a></dt></dl></dd><dt>2.3. <a href="apb.html#N106A0">The runtime</a></dt><dd><dl><dt>Q: <a href="apb.html#N106A5">How is Tamino supported?</a></dt><dt>Q: <a href="apb.html#N106B5">How is XML:DB supported?</a></dt></dl></dd></dl><table summary="Q and A Set" border="0"><col align="left" width="1%"><tbody><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N10618"></a><h3 class="title"><a name="N10618"></a>2.1. General questions</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N1061D">What is it?</a></dt><dt>Q: <a href="apb.html#N10624">Why should I choose JaxMe and not JAXB?</a></dt><dt>Q: <a href="apb.html#N10639">Why the name "JaxMe"?</a></dt><dt>Q: <a href="apb.html#N10642">Are there any reference projects?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>This subsection contains questions co
ncerning the whole project as such.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N1061D"></a><a name="N1061E"></a><b>Q:</b></td><td valign="top" align="left"><p>What is it?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix B. FAQ</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="apa.html" title="Appendix A. License"><link rel="next" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Appendix B. FAQ</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="apa.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="
N1061E"></a>Appendix B. FAQ</h2></div></div></div><p>This section contains a list of frequently asked questions. And, of course, their answers. :-)</p><div class="qandaset"><dl><dt>B.1. <a href="apb.html#N10625">General questions</a></dt><dd><dl><dt>Q: <a href="apb.html#N1062A">What is it?</a></dt><dt>Q: <a href="apb.html#N10631">Why should I choose JaxMe and not JAXB?</a></dt><dt>Q: <a href="apb.html#N10646">Why the name "JaxMe"?</a></dt><dt>Q: <a href="apb.html#N1064F">Are there any reference projects?</a></dt></dl></dd><dt>B.2. <a href="apb.html#N1065E">The Generator</a></dt><dd><dl><dt>Q: <a href="apb.html#N10663">What is the supported subset of XML Schema?</a></dt><dt>Q: <a href="apb.html#N10680">What is the supported subset of JAXB?</a></dt><dt>Q: <a href="apb.html#N1068E">How is the EJB support working?</a></dt><dt>Q: <a href="apb.html#N10699">What are JaxMe's "find methods" and "list methods"?</a></dt><dt>Q: <a href="apb.html#N106A4">Why are the field nam
es uppercased when using the JaxMeJdbcSG?</a></dt></dl></dd><dt>B.3. <a href="apb.html#N106AD">The runtime</a></dt><dd><dl><dt>Q: <a href="apb.html#N106B2">How is Tamino supported?</a></dt><dt>Q: <a href="apb.html#N106C2">How is XML:DB supported?</a></dt></dl></dd></dl><table summary="Q and A Set" border="0"><col align="left" width="1%"><tbody><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N10625"></a><h3 class="title"><a name="N10625"></a>B.1. General questions</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N1062A">What is it?</a></dt><dt>Q: <a href="apb.html#N10631">Why should I choose JaxMe and not JAXB?</a></dt><dt>Q: <a href="apb.html#N10646">Why the name "JaxMe"?</a></dt><dt>Q: <a href="apb.html#N1064F">Are there any reference projects?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>This subsection contains questions concerning th
e whole project as such.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N1062A"></a><a name="N1062B"></a><b>Q:</b></td><td valign="top" align="left"><p>What is it?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>
JaxMe 2 is an implementation of JAXB, the specification for Java/XML binding. In short you can
describe JaxMe as a source generator that takes various sources as input (for example, an XML schema,
a DTD, a Java bean class) and creates sources that allow you to convert a matching XML document into
a Java object or vice versa, convert the Java object into XML. JaxMe extends JAXB with a lot of features.
- See the next question on that topic.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10624"></a><a name="N10625"></a><b>Q:</b></td><td valign="top" align="left"><p>Why should I choose JaxMe and not JAXB?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>That's definitely a question you should ask yourself. The JAXB reference implementation is
+ See the next question on that topic.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10631"></a><a name="N10632"></a><b>Q:</b></td><td valign="top" align="left"><p>Why should I choose JaxMe and not JAXB?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>That's definitely a question you should ask yourself. The JAXB reference implementation is
implemented by a team of excellent technicians who have a vision. It is supported by Sun and other
large vendors.</p><p>On the other hand, you should understand that JAXB has a limited scope. As a reference
implementation, it has to follow the specification, but can hardly do a step beyond. And in
@@ -32,43 +32,43 @@
layer translates "create", "update", "delete" or "read" operations into a set of SQL
instructions. These SQL instructions are performed by JaxMe on your demand. There is almost
no difference (besides the structural limitations, of course) between working with an SQL
- database and an XML database.</li></ol></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10639"></a><a name="N1063A"></a><b>Q:</b></td><td valign="top" align="left"><p>Why the name "JaxMe"?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>After working with JAXP, JAXB, JAXM and all the other stuff for quite some time I began to
+ database and an XML database.</li></ol></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10646"></a><a name="N10647"></a><b>Q:</b></td><td valign="top" align="left"><p>Why the name "JaxMe"?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>After working with JAXP, JAXB, JAXM and all the other stuff for quite some time I began to
automatically associate "JAXsomethingE" with anything related to Java and XML. So this is "Me"
JAX or JaxMe.</p><p>The name is ridiculous. I know. Sometimes we'll probably find something better. (And, who
- knows, perhaps we even find someone changing the sources then ... :-)</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10642"></a><a name="N10643"></a><b>Q:</b></td><td valign="top" align="left"><p>Are there any reference projects?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, JaxMe 2 isn't sufficiently mature for large projects.
+ knows, perhaps we even find someone changing the sources then ... :-)</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N1064F"></a><a name="N10650"></a><b>Q:</b></td><td valign="top" align="left"><p>Are there any reference projects?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, JaxMe 2 isn't sufficiently mature for large projects.
However, JaxMe 1 has been used for really serious issues:
<div class="itemizedlist"><ul type="disc"><li>FleetBoard (http://www.fleetboard.com/) is a telematics and logistics solution.
Large parts of it are realized with the JaxMe EJB generator and a DB2 database as the
backend. Other parts are based on a JaxMe predecessor and Tamino.</li><li>Justus II (http://www.softwareag.com/germany/referenzen/PDF/CR_Justus_D.pdf) is
a large XML application running on Tomcat and an Oracle database as the backend. It is
built from the ground up using JaxMe.</li></ul></div>
- </p><p>If you know of other projects, please let us know.</p></td></tr><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N10651"></a><h3 class="title"><a name="N10651"></a>2.2. The Generator</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N10656">What is the supported subset of XML Schema?</a></dt><dt>Q: <a href="apb.html#N10673">What is the supported subset of JAXB?</a></dt><dt>Q: <a href="apb.html#N10681">How is the EJB support working?</a></dt><dt>Q: <a href="apb.html#N1068C">What are JaxMe's "find methods" and "list methods"?</a></dt><dt>Q: <a href="apb.html#N10697">Why are the field names uppercased when using the JaxMeJdbcSG?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>The following questions are related to the JaxMe generator</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10656"></a><a name="N10
657"></a><b>Q:</b></td><td valign="top" align="left"><p>What is the supported subset of XML Schema?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following is supported:
+ </p><p>If you know of other projects, please let us know.</p></td></tr><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N1065E"></a><h3 class="title"><a name="N1065E"></a>B.2. The Generator</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N10663">What is the supported subset of XML Schema?</a></dt><dt>Q: <a href="apb.html#N10680">What is the supported subset of JAXB?</a></dt><dt>Q: <a href="apb.html#N1068E">How is the EJB support working?</a></dt><dt>Q: <a href="apb.html#N10699">What are JaxMe's "find methods" and "list methods"?</a></dt><dt>Q: <a href="apb.html#N106A4">Why are the field names uppercased when using the JaxMeJdbcSG?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>The following questions are related to the JaxMe generator</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10663"></a><a name="N10
664"></a><b>Q:</b></td><td valign="top" align="left"><p>What is the supported subset of XML Schema?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following is supported:
<div class="itemizedlist"><ul type="disc"><li>All simple datatypes, excluding time intervals (minor issue, some hours work,
if anyone needs it)</li><li>Atomic elements, with and without attributes</li><li>Complex elements with content type empty, sequence, choice, or all.</li><li>Groups (but not nested groups)</li></ul></div></p><p>The following is not yet supported:
<div class="itemizedlist"><ul type="disc"><li>Complex elements with simple content (minor issue, mainly requires writing a
- test suite)</li><li>Mixed content</li><li>Wildcards</li><li>Key specifications</li><li>Recursion (Minor issue, mainly requires writing a test suite)</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10673"></a><a name="N10674"></a><b>Q:</b></td><td valign="top" align="left"><p>What is the supported subset of JAXB?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Lots of features are missing, in particular:
- <div class="itemizedlist"><ul type="disc"><li>External schema binding (requires writing a stylesheet generator)</li><li>Model group binding</li><li>Mixed content</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10681"></a><a name="N10682"></a><b>Q:</b></td><td valign="top" align="left"><p>How is the EJB support working?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following applies for JaxMe 1 only.
+ test suite)</li><li>Mixed content</li><li>Wildcards</li><li>Key specifications</li><li>Recursion (Minor issue, mainly requires writing a test suite)</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10680"></a><a name="N10681"></a><b>Q:</b></td><td valign="top" align="left"><p>What is the supported subset of JAXB?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Lots of features are missing, in particular:
+ <div class="itemizedlist"><ul type="disc"><li>External schema binding (requires writing a stylesheet generator)</li><li>Model group binding</li><li>Mixed content</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N1068E"></a><a name="N1068F"></a><b>Q:</b></td><td valign="top" align="left"><p>How is the EJB support working?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following applies for JaxMe 1 only.
EJB support is not yet included in JaxMe 2. This will hopefully change soon.</p><p>JaxMe 1 contains a generator for entity beans with bean managed persistence.
In short these can very well be compared with CMP entity beans, only you use JaxMe
to create it and the query language is unavailable. On the other hand, they are
typically faster, because they follow the design pattern of value objects.</p><p>The bean generator also supports the generation of stateless session beans that perform
- queries and return XML data. (So called list methods.)</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N1068C"></a><a name="N1068D"></a><b>Q:</b></td><td valign="top" align="left"><p>What are JaxMe's "find methods" and "list methods"?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following applies for JaxMe 1 only.
+ queries and return XML data. (So called list methods.)</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10699"></a><a name="N1069A"></a><b>Q:</b></td><td valign="top" align="left"><p>What are JaxMe's "find methods" and "list methods"?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>As of this writing, the following applies for JaxMe 1 only.
EJB support is not yet included in JaxMe 2. This will hopefully change soon.</p><p>You know what an SQL view is? Forgetting updateable views, one could describe them as a
stored query, that returns some data in a fixed format. In essence this is what JaxMe's find
and list methods are: You specify a query that is compiled by the source code generator. The
result are Java sources that can perform the specified query, possibly configured with some
parameters that you specify as well.</p><p>The difference between find and list methods is that the former return objects which you
may modify and store back. So find methods are somewhat closer to updateable views, because
- they are bound to a specific table.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N10697"></a><a name="N10698"></a><b>Q:</b></td><td valign="top" align="left"><p>Why are the field names uppercased when using the JaxMeJdbcSG?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Field names are built from column names, which are in turn read via JDBC metadata.
+ they are bound to a specific table.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N106A4"></a><a name="N106A5"></a><b>Q:</b></td><td valign="top" align="left"><p>Why are the field names uppercased when using the JaxMeJdbcSG?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Field names are built from column names, which are in turn read via JDBC metadata.
However, most databases are storing column names uppercased internally.</p><p>As a workaround, you may specify an alternative field name. See the IPADDRESS column
- in the Session example for how to do that.</p></td></tr><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N106A0"></a><h3 class="title"><a name="N106A0"></a>2.3. The runtime</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N106A5">How is Tamino supported?</a></dt><dt>Q: <a href="apb.html#N106B5">How is XML:DB supported?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>The following questions are related to the JaxMe runtime.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N106A5"></a><a name="N106A6"></a><b>Q:</b></td><td valign="top" align="left"><p>How is Tamino supported?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Software AG, the vendor of Tamino, is the employer of Jochen Wiedmann (JaxMe's head
+ in the Session example for how to do that.</p></td></tr><tr class="qandadiv"><td colspan="2" valign="top" align="left"><a name="N106AD"></a><h3 class="title"><a name="N106AD"></a>B.3. The runtime</h3></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><dl><dt>Q: <a href="apb.html#N106B2">How is Tamino supported?</a></dt><dt>Q: <a href="apb.html#N106C2">How is XML:DB supported?</a></dt></dl></td></tr><tr colspan="2" class="toc"><td colspan="2" valign="top" align="left"><p>The following questions are related to the JaxMe runtime.</p></td></tr><tr class="question"><td valign="top" align="left"><a name="N106B2"></a><a name="N106B3"></a><b>Q:</b></td><td valign="top" align="left"><p>How is Tamino supported?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>Software AG, the vendor of Tamino, is the employer of Jochen Wiedmann (JaxMe's head
developer). Jochen uses Tamino in his daily work, so support for Tamino is essential. He
considers work with Tamino as definitely much more fun than using DB2, Oracle, or
whatsoever.</p><p>The current Tamino manager is a simple thing implementing native HTTP access to Tamino.
It is a generic manager, not a specific manager per document type. (Working with XML databases
is much simpler for an XML application than using JDBC.) However, the following is not yet
supported, although it really should:
- <div class="itemizedlist"><ul type="disc"><li>Tamino transactions</li><li>Find and list methods (truly important for the XQuery language)</li><li>Use of the official TaminoAPI4J (the current manager is based on a simple SAX handler)</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N106B5"></a><a name="N106B6"></a><b>Q:</b></td><td valign="top" align="left"><p>How is XML:DB supported?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>There is a generic XmlDbManager, which is tested in a JUnit test against eXist. It
+ <div class="itemizedlist"><ul type="disc"><li>Tamino transactions</li><li>Find and list methods (truly important for the XQuery language)</li><li>Use of the official TaminoAPI4J (the current manager is based on a simple SAX handler)</li></ul></div></p></td></tr><tr class="question"><td valign="top" align="left"><a name="N106C2"></a><a name="N106C3"></a><b>Q:</b></td><td valign="top" align="left"><p>How is XML:DB supported?</p></td></tr><tr class="answer"><td valign="top" align="left"><b>A:</b></td><td valign="top" align="left"><p>There is a generic XmlDbManager, which is tested in a JUnit test against eXist. It
is a generic manager, not a specific manager per document type. (Working with XML databases
is much simpler for an XML application than using JDBC.) However, so far no productive use
- is known.</p></td></tr></tbody></table></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="apa.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="go01.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Appendix 1. License </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Glossary</td></tr></table></div></body></html>
\ No newline at end of file
+ is known.</p></td></tr></tbody></table></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="apa.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="go01.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Appendix A. License </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Glossary</td></tr></table></div></body></html>
\ No newline at end of file
Modified: webservices/site/trunk/targets/jaxme/manual/ch01.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/ch01.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/ch01.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/ch01.html Fri Jan 6 15:20:47 2006
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. First steps</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="pr01.html" title="Introduction"><link rel="next" href="ch01s02.html" title="Working with XML"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 1. First steps</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="pr01.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="titl
e"><a name="N10023"></a>Chapter 1. First steps</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch01.html#N10037">Generating Java Code</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01.html#N1003C">Creating a JaxMe Schema</a></span></dt><dt><span class="sect2"><a href="ch01.html#N10053">Running The Generator</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch01s02.html">Working with XML</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01s02.html#N10120">Writing XML Documents</a></span></dt><dt><span class="sect2"><a href="ch01s02.html#N10151">Reading XML</a></span></dt></dl></dd></dl></div><p>This chapter introduces the first steps of using JaxMe. In what follows,
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. First steps</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="pr01.html" title="Introduction"><link rel="next" href="ch01s02.html" title="Working with XML"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 1. First steps</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="pr01.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="titl
e"><a name="N10023"></a>Chapter 1. First steps</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch01.html#N10037">Generating Java Code</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01.html#N1003C">Creating a JaxMe Schema</a></span></dt><dt><span class="sect2"><a href="ch01.html#N10053">Running The Generator</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch01s02.html">Working with XML</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01s02.html#N10120">Writing XML Documents</a></span></dt><dt><span class="sect2"><a href="ch01s02.html#N10151">Reading XML</a></span></dt></dl></dd></dl></div><p>This chapter introduces the first steps of using JaxMe. In what follows,
we will create some simple examples. All examples deal with addresses
stored in XML documents like the following (quoted from the file
<code class="filename">examples/misc/address.xml</code> in the JaxMe 2 distribution):
@@ -35,8 +35,8 @@
name.setSur("Doe");
name.setInitials("JD");
...
- </pre></p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10037"></a>Generating Java Code</h2></div></div><div></div></div><p>After you've downloaded JaxMe, you're ready to use it. In this section
- we will demonstrate how to generate sources.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1003C"></a>Creating a JaxMe Schema</h3></div></div><div></div></div><p>
+ </pre></p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10037"></a>Generating Java Code</h2></div></div></div><p>After you've downloaded JaxMe, you're ready to use it. In this section
+ we will demonstrate how to generate sources.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1003C"></a>Creating a JaxMe Schema</h3></div></div></div><p>
The usual way to use JaxMe is to start from a schema and generate source code
from that schema. So (with the address example in mind) we create an XML Schema
from which the sources will be generated. When using JaxMe in the wild sometimes
@@ -88,7 +88,7 @@
are very expressive (which is why they support source generation so well) but
with this expressiveness comes complexity. Getting to grips with the XML schema
standard is worth the effort but some users may choose to use one of the numerous tools
- that help with XML schema generation.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10053"></a>Running The Generator</h3></div></div><div></div></div><p>The easiest way to run the generator is by invoking an Ant task. Here is a typical ant target:
+ that help with XML schema generation.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10053"></a>Running The Generator</h3></div></div></div><p>The easiest way to run the generator is by invoking an Ant task. Here is a typical ant target:
<pre class="programlisting">
<target name="taskdef">
<!--
Modified: webservices/site/trunk/targets/jaxme/manual/ch01s02.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/ch01s02.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/ch01s02.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/ch01s02.html Fri Jan 6 15:20:47 2006
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Working with XML</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="ch01.html" title="Chapter 1. First steps"><link rel="prev" href="ch01.html" title="Chapter 1. First steps"><link rel="next" href="ch02.html" title="Chapter 2. Reference"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Working with XML</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01.html">Prev</a> </td><th align="center" width="60%">Chapter 1. First steps</th><td align="right" width="20%"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="tit
lepage"><div><div><h2 class="title" style="clear: both"><a name="N10113"></a>Working with XML</h2></div></div><div></div></div><p>In this section we'll show how to create XML from the beans generated earlier.
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Working with XML</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="ch01.html" title="Chapter 1. First steps"><link rel="prev" href="ch01.html" title="Chapter 1. First steps"><link rel="next" href="ch02.html" title="Chapter 2. Reference"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Working with XML</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01.html">Prev</a> </td><th align="center" width="60%">Chapter 1. First steps</th><td align="right" width="20%"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="tit
lepage"><div><div><h2 class="title" style="clear: both"><a name="N10113"></a>Working with XML</h2></div></div></div><p>In this section we'll show how to create XML from the beans generated earlier.
XML (or better an XML document) exists in various
flavours: you might want to have it serialized into a String or you may prefer character or
byte streams (typically instances of <code class="classname">Writer</code> or <code class="classname">OutputStream</code>).
@@ -6,7 +6,7 @@
efficient on other occasions.</p><p>
The important questions are: how do I
create a serialized XML document (a String, a character or byte stream)? And, vice versa, how
- do I read such a document and convert it back into Java objects?</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10120"></a>Writing XML Documents</h3></div></div><div></div></div><p>In the case of JaxMe, you'll start from simple Java beans whose source has typically
+ do I read such a document and convert it back into Java objects?</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10120"></a>Writing XML Documents</h3></div></div></div><p>In the case of JaxMe, you'll start from simple Java beans whose source has typically
been generated. An address implementation is constructed by instantiating
an <code class="classname">AddressImpl</code> (which implements <code class="classname">Address</code>).
For example:
@@ -75,7 +75,7 @@
and <code class="classname">Marshaller</code> are used. These objects are specified by
<span class="acronym">JAXB</span>. The example uses no JaxMe specific
features and should run with any compliant JAXB implementation.</li></ul></div>
- </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10151"></a>Reading XML</h3></div></div><div></div></div><p>The example on writing XML was surprisingly simple. In fact, the only
+ </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10151"></a>Reading XML</h3></div></div></div><p>The example on writing XML was surprisingly simple. In fact, the only
nasty part was creating the object, which requires invocation of lots of
setters and getters. Quite opposed to the marshalling, which took place in
three lines. And, as we soon will see: unmarshalling (the process of reading
Modified: webservices/site/trunk/targets/jaxme/manual/ch02.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/ch02.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/ch02.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/ch02.html Fri Jan 6 15:20:47 2006
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Reference</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="ch01s02.html" title="Working with XML"><link rel="next" href="ch02s02.html" title="Marshalling objects"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 2. Reference</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 cl
ass="title"><a name="N10193"></a>Chapter 2. Reference</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch02.html#N10199">The JaxMe Ant Task</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02.html#N102D7">The Up-to-date check</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s02.html">Marshalling objects</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02s02.html#N102F1">Marshaller methods</a></span></dt><dt><span class="sect2"><a href="ch02s02.html#N103D2">Marshaller properties</a></span></dt></dl></dd></dl></div><p>This chapter is more formal and can be assumed to be the JaxMe reference documentation.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10199"></a>The JaxMe Ant Task</h2></div></div><div></div></div><p>The JaxMe Ant task was written with the following goals in mind:
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Reference</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="ch01s02.html" title="Working with XML"><link rel="next" href="ch02s02.html" title="Marshalling objects"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 2. Reference</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 cl
ass="title"><a name="N10193"></a>Chapter 2. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch02.html#N10199">The JaxMe Ant Task</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02.html#N102E4">The Up-to-date check</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s02.html">Marshalling objects</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02s02.html#N102FE">Marshaller methods</a></span></dt><dt><span class="sect2"><a href="ch02s02.html#N103DF">Marshaller properties</a></span></dt></dl></dd></dl></div><p>This chapter is more formal and can be assumed to be the JaxMe reference documentation.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10199"></a>The JaxMe Ant Task</h2></div></div></div><p>The JaxMe Ant task was written with the following goals in mind:
<div class="itemizedlist"><ul type="disc"><li>To preserve as much compatibility as possible with the JAXB xjc task</li><li>To provide access to JaxMe extensions</li></ul></div>
In other words, if you have existing build scripts using JAXB's xjc, you should
be able to convert them to JaxMe with a single switch (by exchanging the
@@ -50,12 +50,18 @@
specified in bytes (stackSize="2097152"), kilobytes (stackSize="2048kb"),
or megabytes (stackSize="2mb").</p>
<p>This attribute is ignored by the JaxMe ant task and present for compatibility
- reasons only. A warning is emitted, if you use it.</p></td><td>JAXB XJC</td><td>No</td></tr><tr><td>target</td><td>Specifies the target directory, where generated sources are being created
- in a package structure. For example, if the "target" attribute has the value
- "src" and the "package" attribute is "com.acme", then the directory
- <code class="filename">src/com/acme</code> will be used.</td><td>JAXB XJC</td><td>No, defaults to the current directory</td></tr><tr><td>validating</td><td>Depending on this attributes value, the XML parser used to parse the XML
+ reasons only. A warning is emitted, if you use it.</p></td><td>JAXB XJC</td><td>No</td></tr><tr><td>resourceTarget</td><td>Specifies the target directory for generating resource files.
+ If required, a package structure is created automatically below
+ the resource target directory. For example, if the "target" attribute
+ has the value "src" and the "package" attribute is "com.acme", then
+ the directory <code class="filename">src/com/acme</code> will be used.
+ </td><td>JaxMe</td><td>No, defaults to the "target" directory</td></tr><tr><td>target</td><td>Specifies the target directory for generating Java source files.
+ If required, a package structure is created automatically below
+ the resource target directory. For example, if the "target" attribute
+ has the value "src" and the "package" attribute is "com.acme", then
+ the directory <code class="filename">src/com/acme</code> will be used.</td><td>JAXB XJC</td><td>No, defaults to the current directory</td></tr><tr><td>validating</td><td>Depending on this attributes value, the XML parser used to parse the XML
schema file will either be validating or not.</td><td>JaxMe</td><td>No, defaults to "false"</td></tr></tbody></table></div></p><p>The ant task also supports the following nested elements:
- <div class="table"><a name="N10239"></a><p class="title"><b>Table 2.2. Nested elements of the JaxMe ant task</b></p><table summary="Nested elements of the JaxMe ant task" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Name</th><th>Description</th><th>Origin</th><th>Multiplicity</th></tr></thead><tbody><tr><td>arg</td><td><p>This nested element is ignored by the JaxMe ant task and exists for
+ <div class="table"><a name="N10246"></a><p class="title"><b>Table 2.2. Nested elements of the JaxMe ant task</b></p><table summary="Nested elements of the JaxMe ant task" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Name</th><th>Description</th><th>Origin</th><th>Multiplicity</th></tr></thead><tbody><tr><td>arg</td><td><p>This nested element is ignored by the JaxMe ant task and exists for
JAXB compatibility only. If this element is present, a warning
will be logged.</p>
<p>In the case of JAXB it specifies additional command line arguments being
@@ -109,7 +115,7 @@
schema reader. An alternative schema reader is, for example,
"org.apache.ws.jaxme.generator.sg.impl.JaxMeSchemaReader"
(a subclass of JAXBSchemaReader with JaxMe specific extensions).</td><td>JaxMe</td><td>0..1</td></tr></tbody></table></div>
- </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N102D7"></a>The Up-to-date check</h3></div></div><div></div></div><p>By default, the JaxMe ant task will always run the generator and create new files.
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N102E4"></a>The Up-to-date check</h3></div></div></div><p>By default, the JaxMe ant task will always run the generator and create new files.
When this task is part of a general ant build script, this behaviour will result
in new files being generated and recompiled each time the build is run.</p><p>To achieve greater efficiency, use the nested <produces> and <depends> elements.
If one or more <produces> element is specified, then an up-to-date check is performed
Modified: webservices/site/trunk/targets/jaxme/manual/ch02s02.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/ch02s02.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/ch02s02.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/ch02s02.html Fri Jan 6 15:20:47 2006
@@ -1,9 +1,9 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Marshalling objects</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="ch02.html" title="Chapter 2. Reference"><link rel="prev" href="ch02.html" title="Chapter 2. Reference"><link rel="next" href="apa.html" title="Appendix 1. License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Marshalling objects</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02.html">Prev</a> </td><th align="center" width="60%">Chapter 2. Reference</th><td align="right" width="20%"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlep
age"><div><div><h2 class="title" style="clear: both"><a name="N102EC"></a>Marshalling objects</h2></div></div><div></div></div><p>This section describes the various ways of marshalling JaxMe objects and
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Marshalling objects</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="ch02.html" title="Chapter 2. Reference"><link rel="prev" href="ch02.html" title="Chapter 2. Reference"><link rel="next" href="apa.html" title="Appendix A. License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Marshalling objects</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02.html">Prev</a> </td><th align="center" width="60%">Chapter 2. Reference</th><td align="right" width="20%"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlep
age"><div><div><h2 class="title" style="clear: both"><a name="N102F9"></a>Marshalling objects</h2></div></div></div><p>This section describes the various ways of marshalling JaxMe objects and
how to configure the marshalling process. Note, that this section uses both
methods and features, which are specified by JAXB and others, which are
proprietary to JaxMe. Explicit remarks will tell you about the latter,
- so that you are still able to write 100% portable code.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N102F1"></a>Marshaller methods</h3></div></div><div></div></div><p>The following methods are specified by JAXB. We'll present each method,
- followed by a small piece of example code.</p><div class="variablelist"><p class="title"><b>Marshaller methods</b></p><dl><dt><span class="term"><code class="function">public void marshal(Object, OutputStream) throws JAXBException</code></span></dt><dd><p>Marshals the object into the given <code class="classname">java.io.OutputStream</code>.</p><div class="example"><a name="N10304"></a><p class="title"><b>Example 2.1. Marshalling into an OutputStream</b></p><pre class="programlisting">
+ so that you are still able to write 100% portable code.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N102FE"></a>Marshaller methods</h3></div></div></div><p>The following methods are specified by JAXB. We'll present each method,
+ followed by a small piece of example code.</p><div class="variablelist"><p class="title"><b>Marshaller methods</b></p><dl><dt><span class="term"><code class="function">public void marshal(Object, OutputStream) throws JAXBException</code></span></dt><dd><p>Marshals the object into the given <code class="classname">java.io.OutputStream</code>.</p><div class="example"><a name="N10311"></a><p class="title"><b>Example 2.1. Marshalling into an OutputStream</b></p><pre class="programlisting">
public void writeToFile(
JAXBContext pContext,
Object pObject,
@@ -23,7 +23,7 @@
Depending on the encoding, the <code class="classname">Marshaller</code> will convert
characters (16 bit entities) into bytes (8 bit entities). The encoding may
also have influence on the marshallers decision, which characters to escape
- using <span class="token">&#ddd;</span> or not.</p></dd><dt><span class="term"><code class="function">public void marshal(Object, Writer) throws JAXBException</code></span></dt><dd><p>Marshals the object into the given <code class="classname">java.io.Writer</code>.</p><div class="example"><a name="N1031D"></a><p class="title"><b>Example 2.2. Marshalling into a Writer</b></p><pre class="programlisting">
+ using <span class="token">&#ddd;</span> or not.</p></dd><dt><span class="term"><code class="function">public void marshal(Object, Writer) throws JAXBException</code></span></dt><dd><p>Marshals the object into the given <code class="classname">java.io.Writer</code>.</p><div class="example"><a name="N1032A"></a><p class="title"><b>Example 2.2. Marshalling into a Writer</b></p><pre class="programlisting">
public void writeToFile(
JAXBContext pContext,
Object pObject,
@@ -42,7 +42,7 @@
}
</pre></div><p>This example is almost equivalent to the previous example with an <code class="classname">OutputStream</code>
as the target. In practice, the result may be slightly different anyways, for example, because the
- <code class="classname">Marshaller</code> may choose a different set of characters to escape.</p><div class="example"><a name="N1032B"></a><p class="title"><b>Example 2.3. Marshalling into a <code class="classname">String</code></b></p><pre class="programlisting">
+ <code class="classname">Marshaller</code> may choose a different set of characters to escape.</p><div class="example"><a name="N10338"></a><p class="title"><b>Example 2.3. Marshalling into a <code class="classname">String</code></b></p><pre class="programlisting">
public String asString(
JAXBContext pContext,
Object pObject)
@@ -66,7 +66,7 @@
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>The <code class="classname">node</code> must be ready to accept an element as a child.
Suitable nodes are, for example, documents, document fragments, or elements.</div>
As an example, we'll demonstrate how to convert the JaxMe object into an instance
- of <code class="classname">org.w3c.dom.Document</code>.</p><div class="example"><a name="N10352"></a><p class="title"><b>Example 2.4. </b></p><pre class="programlisting">
+ of <code class="classname">org.w3c.dom.Document</code>.</p><div class="example"><a name="N1035F"></a><p class="title"><b>Example 2.4. </b></p><pre class="programlisting">
public Document asDOMDocument(
JAXBContext pContext,
Object pObject,
@@ -91,7 +91,7 @@
is implemented by the <code class="classname">XMLWriter</code>, which is just an extension of the
<code class="classname">ContentHandler</code>. As an example, we'll demonstrate how to transform a
JaxMe object using an XSL stylesheet, writing the result into an <code class="classname">OutputStream</code>:
- </p><div class="example"><a name="N1036F"></a><p class="title"><b>Example 2.5. Transformation of a JaxMe object using an XSL stylesheet</b></p><pre class="programlisting">
+ </p><div class="example"><a name="N1037C"></a><p class="title"><b>Example 2.5. Transformation of a JaxMe object using an XSL stylesheet</b></p><pre class="programlisting">
public void transformToFile(JAXBContext pContext,
Object pObject,
TransformerFactory pFactory,
@@ -137,7 +137,7 @@
has no useful methods at all. In other words, a new implementation can only be used, if all
users of the <code class="classname">Result</code> know how to deal with it. In our case the users
include <span class="application">JaxMe</span>.</p><p>The above limitations are best described, if we use the <span class="application">JaxMe</span>
- implementation of the method as an example:</p><div class="example"><a name="N103C4"></a><p class="title"><b>Example 2.6. <span class="application">JaxMe</span>'s implementation of the <code class="classname">Result</code>
+ implementation of the method as an example:</p><div class="example"><a name="N103D1"></a><p class="title"><b>Example 2.6. <span class="application">JaxMe</span>'s implementation of the <code class="classname">Result</code>
destination</b></p><pre class="programlisting">
public void marshal(Object pObject, Result pResult)
throws JAXBException {
@@ -189,10 +189,10 @@
others we've seen so far. (Funny enough, it would have been possible to go the
other way and implement all others as wrappers around this one. However, that
would require the presence of an XSLT implementation at runtime and most
- possibly quite inefficient.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N103D2"></a>Marshaller properties</h3></div></div><div></div></div><p>In the previous section we've already seen how to configure the <code class="classname">Marshaller</code>'s
+ possibly quite inefficient.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N103DF"></a>Marshaller properties</h3></div></div></div><p>In the previous section we've already seen how to configure the <code class="classname">Marshaller</code>'s
encoding by setting a <span class="token">property</span>. In this section we'll present a complete list of all
the properties supported by the <span class="application">JaxMe</span> <code class="classname">Marshaller</code>.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N103E4"></a><span class="acronym">JAXB</span> standard <code class="classname">Marshaller</code> properties</h4></div></div><div></div></div><p>The following properties are part by the <span class="acronym">JAXB</span> specification. In other
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N103F1"></a><span class="acronym">JAXB</span> standard <code class="classname">Marshaller</code> properties</h4></div></div></div><p>The following properties are part by the <span class="acronym">JAXB</span> specification. In other
words: You are safe to use them with any <span class="acronym">JAXB</span> compliant implementation,
including <span class="application">JaxMe</span>. Whenever possible, we recommend to use only this
properties and no others.</p><div class="variablelist"><p class="title"><b><span class="acronym">JAXB</span> standard <code class="classname">Marshaller</code> properties</b></p><dl><dt><span class="term"><span class="token">jaxb.encoding</span>, </span><span class="term"><code class="classname">Marshaller</code>.<code class="constant">JAXB_ENCODING</code></span></dt><dd><p>As we have already seen, this property specifies the encoding used by the
@@ -225,7 +225,7 @@
</pre>
The following example turns off the default handling and creates a String containing
- unformatted XML:</p><div class="example"><a name="N1044B"></a><p class="title"><b>Example 2.7. Creating unformatted XML</b></p><pre class="programlisting">
+ unformatted XML:</p><div class="example"><a name="N10458"></a><p class="title"><b>Example 2.7. Creating unformatted XML</b></p><pre class="programlisting">
public String asUnformattedString(
JAXBContext pContext,
Object pObject,
@@ -242,7 +242,7 @@
return sw.toString();
}
- </pre></div></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10451"></a><span class="application">JaxMe</span> specific <code class="classname">Marshaller</code>properties</h4></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3>The following properties must not be used for portable applications, because they are
+ </pre></div></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1045E"></a><span class="application">JaxMe</span> specific <code class="classname">Marshaller</code>properties</h4></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3>The following properties must not be used for portable applications, because they are
proprietary to <span class="application">JaxMe</span>.</div><div class="variablelist"><p class="title"><b><span class="application">JaxMe</span> specific <code class="classname">Marshaller</code>properties</b></p><dl><dt><span class="term"><span class="token">jaxme.datatype.converter</span>, </span><span class="term"><code class="classname">JMControllerImpl</code>.<code class="constant">JAXME_DATATYPE_CONVERTER</code></span></dt><dd><p>The <code class="classname">javax.xml.bind.DatatypeConverterInterface</code> is used by
<span class="acronym">JAXB</span> implementations to convert various data types into strings
and vice versa. For example, there is a method <code class="function">parseInt(String)</code>,
@@ -267,7 +267,7 @@
If your XML instances conform to the XML Schema format, it is most likely that you won't
have interoperability problems with foreign software. Fact is, however, that
not all of us are working in a multinational environment and prefer human readable
- formats and local time.</p><div class="example"><a name="N104B2"></a><p class="title"><b>Example 2.8. Using a custom datatype converter</b></p><pre class="programlisting">
+ formats and local time.</p><div class="example"><a name="N104BF"></a><p class="title"><b>Example 2.8. Using a custom datatype converter</b></p><pre class="programlisting">
// Create a subclass of the JaxMe datatype converter, overriding its parseDateTime() and
// printDateTime() methods.
public class MyDatatypeConverter extends org.apache.ws.jaxme.impl.DatatypeConverterImpl {
@@ -335,7 +335,7 @@
which version of Windows you choose, it remains the same after 20 years of development:
You'll see a text file containing a single line and where you'd expect the lines being
splitted, the editor will show you black boxes only. But rumbling doesn't help, we've got
- to live with it.</p><p>The following example shows how to turn on Windows line terminators:</p><div class="example"><a name="N104F5"></a><p class="title"><b>Example 2.9. Turning on Windows line terminators</b></p><pre class="programlisting">
+ to live with it.</p><p>The following example shows how to turn on Windows line terminators:</p><div class="example"><a name="N10502"></a><p class="title"><b>Example 2.9. Turning on Windows line terminators</b></p><pre class="programlisting">
public String asUnformattedString(
JAXBContext pContext,
Object pObject,
@@ -401,7 +401,7 @@
By default JaxMe does not create such a declaration, because that would make it difficult
to embed the resulting XML into a larger document.</p><p>An XML declaration is particularly important, if you use another encoding than
<code class="constant">UTF-8</code>. In that case you should consider a declaration as
- mandatory.</p><p>The property has no effect, when marshalling to DOM trees, or SAX handlers.</p><div class="example"><a name="N10565"></a><p class="title"><b>Example 2.10. Enabling an XML declaration</b></p><pre class="programlisting">
+ mandatory.</p><p>The property has no effect, when marshalling to DOM trees, or SAX handlers.</p><div class="example"><a name="N10572"></a><p class="title"><b>Example 2.10. Enabling an XML declaration</b></p><pre class="programlisting">
// Convert a JaxMe object into a String, using the above converter
public String asString(JAXBContext pContext, Object pObject)
throws JAXBException {
@@ -427,7 +427,7 @@
encoding, escaping all Unicode points above 126.</p></dd><dt><span class="term"><code class="classname">org.apache.ws.jaxme.impl.CharSetXMLWriter</code></span></dt><dd><p>This implementation is used, whenever you are running Java 1.4 or newer.
It is internally using the class <code class="classname">java.nio.charset.CharsetEncoder</code>
to determine the Unicode points being escaped.</p></dd><dt><span class="term"><code class="classname">org.apache.ws.jaxme.impl.PassThroughXMLWriter</code></span></dt><dd><p>This implementation does no escaping at all.</p></dd></dl></div></p><p>As an example, we'll write and use and <code class="classname">XMLWriter</code> which is
- escaping the german Umlauts, but no other characters.</p><div class="example"><a name="N105B0"></a><p class="title"><b>Example 2.11. Implementation of an XMLWriter escaping german Umlauts</b></p><pre class="programlisting">
+ escaping the german Umlauts, but no other characters.</p><div class="example"><a name="N105BD"></a><p class="title"><b>Example 2.11. Implementation of an XMLWriter escaping german Umlauts</b></p><pre class="programlisting">
public class UmlautXMLWriter extends org.apache.ws.jaxme.impl.XMLWriterImpl {
protected boolean canEncode(char c) {
switch (c) {
@@ -458,4 +458,4 @@
return sw.toString();
}
- </pre></div></dd></dl></div></div></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch02.html">Prev</a> </td><td align="center" width="20%"><a accesskey="u" href="ch02.html">Up</a></td><td align="right" width="40%"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Chapter 2. Reference </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Appendix 1. License</td></tr></table></div></body></html>
\ No newline at end of file
+ </pre></div></dd></dl></div></div></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch02.html">Prev</a> </td><td align="center" width="20%"><a accesskey="u" href="ch02.html">Up</a></td><td align="right" width="40%"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Chapter 2. Reference </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Appendix A. License</td></tr></table></div></body></html>
\ No newline at end of file
Modified: webservices/site/trunk/targets/jaxme/manual/go01.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/jaxme/manual/go01.html?rev=366595&r1=366594&r2=366595&view=diff
==============================================================================
--- webservices/site/trunk/targets/jaxme/manual/go01.html (original)
+++ webservices/site/trunk/targets/jaxme/manual/go01.html Fri Jan 6 15:20:47 2006
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><meta content="DocBook XSL Stylesheets V1.69.0" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="apb.html" title="Appendix 2. FAQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Glossary</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="apb.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> </td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="N106BD"></a>Glossary</h2></div></div><div></div></div><dl><dt><a name="BSDLicense"></a>BSD License</dt><dd><p>One of the worlds most importan
t open source licenses, originally developed
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><meta content="DocBook XSL Stylesheets V1.68.1" name="generator"><link rel="start" href="index.html" title="The JaxMe 2 manual"><link rel="up" href="index.html" title="The JaxMe 2 manual"><link rel="prev" href="apb.html" title="Appendix B. FAQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Glossary</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="apb.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> </td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="N106CA"></a>Glossary</h2></div></div></div><dl><dt><a name="BSDLicense"></a>BSD License</dt><dd><p>One of the worlds most important open sour
ce licenses, originally developed
for BSD Unix. It is very liberal: Basically it allows you to redistribute both sources and binaries,
as you want. Unlike the GPL you may even sell derivated works. See also
<a href="http://www.opensource.org/licenses/bsd-license.php" target="_top">
@@ -7,4 +7,4 @@
is the SUN specification for Java/XML binding.
It is also available as a reference implementation. JaxMe aims to become another
JAXB implementation at some time. However, full JAXB support is far from complete.
- </p></dd></dl></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="apb.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> </td></tr><tr><td valign="top" align="left" width="40%">Appendix 2. FAQ </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> </td></tr></table></div></body></html>
\ No newline at end of file
+ </p></dd></dl></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="apb.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> </td></tr><tr><td valign="top" align="left" width="40%">Appendix B. FAQ </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> </td></tr></table></div></body></html>
\ No newline at end of file