You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jaxme-dev@ws.apache.org by rd...@apache.org on 2004/07/06 22:10:11 UTC

cvs commit: ws-jaxme/src/documentation/manual jaxme2.xml

rdonkin     2004/07/06 13:10:11

  Modified:    src/documentation/manual Tag: Branch_R0_3 jaxme2.xml
  Log:
  Small improvements to documentation
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.2.2.2   +13 -10    ws-jaxme/src/documentation/manual/jaxme2.xml
  
  Index: jaxme2.xml
  ===================================================================
  RCS file: /home/cvs/ws-jaxme/src/documentation/manual/jaxme2.xml,v
  retrieving revision 1.2.2.1
  retrieving revision 1.2.2.2
  diff -u -r1.2.2.1 -r1.2.2.2
  --- jaxme2.xml	27 Jun 2004 20:27:17 -0000	1.2.2.1
  +++ jaxme2.xml	6 Jul 2004 20:10:11 -0000	1.2.2.2
  @@ -36,26 +36,29 @@
   </bookinfo>
   <preface><title>Introduction</title>
   <para>JaxMe 2 is a Java source generator. It is used as the base of XML
  -application frameworks. Using JaxMe, you get code that
  +application frameworks. Using JaxMe can generate code that can:
   <itemizedlist>
  -  <listitem>Converts XML documents into Java beans</listitem>
  -  <listitem>Stores Java beans into a database. It is recommended to use
  +  <listitem>Convert XML documents into Java beans and back to XML documents again.</listitem>
  +  <listitem>Persist those Java beans into a datastore. It is recommended to use
       an XML database as a backend, but relational databases are supported
  -    through an objectrelational mapper. (If your XML documents are
  -    sufficiently simple, that is.) It is even possible to mix different
  -    database engines, depending on the document type.</listitem>
  +    through an object-relational mapper. (If your XML documents are
  +    sufficiently simple, that is ;) It is even possible to mix different
  +    database engines, depending on the document type.
  +    JaxMePM (the JaxMe persistence management framework) is design to be extensible.
  +    Developers can create new implementations to add support for datastores
  +    that JaxMe does not support out-of-the-box.
  +    </listitem>
     <listitem>Query the database for previously stored data and convert
       this data into Java beans.</listitem>
     <listitem>The database can be accessed directly or by EJB entity or
       session beans. These beans may be generated by JaxMe.</listitem>
  -  <listitem>Finally, Java beans can be mapped into XML.</listitem>
   </itemizedlist>
  -If you follow the above items, you will note, that the complete workflow
  -of a typical application is supported: Gathering, storing, processing,
  +So, the complete workflow
  +of a typical application is supported: gathering, storing, processing,
   and presenting data.</para>
   <para>JaxMe is an open source project: You may redistribute sources, or
   binaries, as you like. JaxMe comes to you under The Apache Software Foundation 
  -License, a very liberal license: You are even allowed to redistribute derived works
  +License, a very liberal license: you are even allowed to redistribute derived works
   under a modified license. This is in contrast to the GPL, which requires
   that derived works are GPL'ed again.</para>
   </preface>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org