User: luke_t  
  Date: 01/12/04 18:07:57

  Modified:    src/xdocs faq.xml
  Log:
  added link to juha's book and some CMP stuff with ref to Dain's CMP 2.0 docs.
  
  Revision  Changes    Path
  3.2       +20 -18    manual/src/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /cvsroot/jboss/manual/src/xdocs/faq.xml,v
  retrieving revision 3.1
  retrieving revision 3.2
  diff -u -r3.1 -r3.2
  --- faq.xml   2001/11/30 02:50:06     3.1
  +++ faq.xml   2001/12/05 02:07:56     3.2
  @@ -6,11 +6,11 @@
   
     <articleinfo>
        <title>JBoss FAQ</title>
  -     <releaseinfo>$Revision: 3.1 $, $Date: 2001/11/30 02:50:06 $</releaseinfo>
  +     <releaseinfo>$Revision: 3.2 $, $Date: 2001/12/05 02:07:56 $</releaseinfo>
        <!--revhistory>
     <revision>
  -  <revnumber>$Revision: 3.1 $</revnumber>
  -  <date>$Date: 2001/11/30 02:50:06 $</date>
  +  <revnumber>$Revision: 3.2 $</revnumber>
  +  <date>$Date: 2001/12/05 02:07:56 $</date>
     </revision>
     </revhistory>
        -->
  @@ -24,7 +24,7 @@
   </abstract>
     -->
   
  -  <qandaset defaultlabel="number">
  +  <qandaset>
   
        <qandadiv id="faq.intro">
          <title>Introduction</title>
  @@ -33,7 +33,7 @@
          <qandaentry id="faq.intro.version">
                <question><para>What is the version of this FAQ and when was it last 
updated?</para></question>
                <answer>
  -               <para>This is $Revision: 3.1 $ of the FAQ. The last update was made 
on $Date: 2001/11/30 02:50:06 $.</para>
  +               <para>This is $Revision: 3.2 $ of the FAQ. The last update was made 
on $Date: 2001/12/05 02:07:56 $.</para>
                </answer>
          </qandaentry>
   
  @@ -153,12 +153,14 @@
                <answer>
                  <para>With respect to Enterprise JavaBeans (EJBs), persistence is a 
term that describes the process whereby the the state of an active (stateful?) EJB is 
stored (usually to a database) in such a way that the EJB can be reactivated later. It 
is serialization for EJBs if you like.</para>
   
  -               <para>There are two flavours of persistence in EJB - Bean-Managed 
Persistence (BMP) and Container-Managed Persistence (CMP). The main difference between 
the two flavours is who is responsible for <emphasis>actually</emphasis> persisting 
the EJB. In BMP the bean developer is responsible for writing the code that persists 
the beans state (maybe using JDBC?) while in CMP, the container is reponsible. In CMP 
a bean developer might not even <emphasis>know</emphasis> what object-relational 
database persistence is let alone how it works?. Pretty neat.</para>
  +               <para>There are two flavours of persistence in EJB - Bean-Managed 
Persistence (BMP) and Container-Managed Persistence (CMP). The main difference between 
the two flavours is who is responsible for <emphasis>actually</emphasis> persisting 
the EJB. In BMP the bean developer is responsible for writing the code that persists 
the bean's state (maybe using JDBC?) while in CMP, the container is reponsible.</para>
   
                  <para>A relevant excerpt from the <ulink 
url="http://java.sun.com/products/ejb/docs.html";>EJB 1.1. specification</ulink> 
itself, on page 100:
   
                        <blockquote><para>The entity bean component protocol allows 
the entity Bean Provider either to implement the entity bean's persistence directly in 
the entity bean class or in one or more helper classes provided with the entity bean 
class (bean-managed persistence), or to delegate the entity bean's persistence to the 
Container Provider tools used at deployment time (container-managed 
persistence).</para></blockquote>
                  </para>
  +
  +               <para>For more on CMP with JBoss, see <xref 
linkend="faq.cmp"/></para>.
                </answer>
          </qandaentry>
   
  @@ -166,7 +168,7 @@
                <question><para>What are these MBeans and JMX that I keep hearing 
about?</para></question>
                <answer>
                  <para><quote>Managed Beans</quote> are part of the Java Management 
Extensions Specification<ulink 
url="http://java.sun.com/products/JavaManagement/";>(JMX)</ulink> (formerly JMAPI). 
This provides an architecture and API for application management using Java. JBoss has 
made JMX its own and it forms the basis of the entire JBoss infrastructure. JBoss is 
basically a series of MBean service components plugged together using JMX as the bus. 
See the <link linkend="design.jmx">design notes</link> for more information.</para>
  -               <para>For an in-depth explanation of JMX and its potential uses, see 
the forthcoming book by Juha Lindfors FIXME ref, date.</para>
  +               <para>For an in-depth explanation of JMX and its potential uses, see 
the forthcoming book <ulink 
url="http://www.samspublishing.com/detail_sams.cfm?item=0672322889";>JMX: Managing J2EE 
with Java Management Extensions</ulink> by Juha Lindfors.</para>
                </answer>
          </qandaentry>
   
  @@ -178,7 +180,6 @@
                          <para>The <ulink 
url="http://java.sun.com/j2ee/j2ee-1_3-fr-spec.pdf";>J2EE Specification</ulink>.</para>
                        </listitem>
                  </itemizedlist>
  -
                </answer>
          </qandaentry>
   
  @@ -483,28 +484,29 @@
        <!-- End of EJB section -->
   
        <!-- CMP stuff -->
  -     <qandadiv>
  +     <qandadiv id="faq.cmp">
          <title>Container-Managed Persistence (CMP)</title>
          <para>CMP implementations, spec versions etc.</para>
   
          <qandaentry>
                <question><para>What is CMP and how do I use it with 
JBoss?</para></question>
                <answer>
  -               <para>...</para>
  -
  +               <para>You can write a basic CMP app. with minimal effort beyond that 
of the standard approach described in the EJB spec.</para>
  +               <para>In JBoss 2.*, the default CMP engine is called Jaws, and you 
can supply additional configuration information by providing a 
<filename>jaws.xml</filename> file in addition to the standard 
<filename>ejb-jar.xml</filename> file.</para>
  +               <para>For JBoss 3.*, see <xref linkend="faq.cmp.cmp2"/></para>
                </answer>
          </qandaentry>
   
  -       <qandaentry>
  +       <qandaentry id="faq.cmp.cmp2">
                <question><para>Does JBoss support the CMP features from EJB 
2.0?</para></question>
                <answer>
  -               <para>Support for EJB 2.0 CMP is a central feature for JBoss 
3.0</para>
  -               <para>You can purchase <ulink 
url="http://www.flashline.com/Components/View.jsp?prodid=4312";>full 
documentation</ulink> for the CMP 2.0 engine, written by the author.</para>
  +               <para>Support for EJB 2.0 CMP is a central feature of JBoss 3.0 and 
is provided by the JBossCMP module, which is the default persistence engine. Advanced 
configuration is achieved by use of the <filename>jbosscmp-jdbc.xml</filename> 
file.</para>
  +               <para>You can purchase a Workbook for the CMP 2.0 engine, written by 
the author, from <ulink 
url="http://www.flashline.com/components/productsbyvendor.jsp?&amp;vendorid=1376";>flashline</ulink>.
 This provides advanced configuration details for JBossCMP, along with example 
code.</para>
                </answer>
          </qandaentry>
   
          <qandaentry>
  -             <question><para>What alternatives are there to the default 
implementation?</para></question>
  +             <question><para>What alternatives are there to the default CMP 
implementation?</para></question>
                <answer>
                  <para>... <!-- Integration with other persistence engines, Cocobase, 
write your own persistence layer?--> </para>
                </answer>
  @@ -542,7 +544,7 @@
          <qandaentry id="faq.resource.newbie">
                <question><para>I'm new to this stuff and I don't even know what a 
DataSource is.</para></question>
                <answer>
  -               <para>A <ulink 
url="http://java.sun.com/j2se/1.4/docs/api/javax/sql/DataSource.html";>DataSource</ulink>
 is the preferred Java abstraction for obtaining database connections. You will 
usually set up datasources as part of your server configuration along with a name 
under which it will be bound in the server's JNDI implementation. The DataSource 
usually also hides the implementation of connection pooling from the client.</para> 
<!-- link to BMP example? -->
  +               <para>A <ulink 
url="http://java.sun.com/j2se/1.4/docs/api/javax/sql/DataSource.html";>DataSource</ulink>
 is the preferred Java abstraction for obtaining database connections. You will 
usually set up datasources as part of your server configuration along with a name 
under which each one will be bound in the server's JNDI implementation. The DataSource 
usually also hides the implementation of connection pooling from the client.</para> 
<!-- link to BMP example? -->
                </answer>
          </qandaentry>
   
  @@ -593,7 +595,7 @@
          <qandaentry>
                <question><para>How do I configure Database X to work with 
JBoss?</para></question>
                <answer>
  -               <para>...</para>
  +               <para>There are database-specific examples in the <link 
linkend="resource-db-specific">manual</link>.</para>
                </answer>
          </qandaentry>
   
  @@ -710,4 +712,4 @@
   
     </qandaset>
   
  -</article>
  +</article>
  \ No newline at end of file
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to