[Apache Geronimo Wiki] Updated: Working with Enterprise JavaBeans

[sc...@geronimo.apache.org]

   Date: 2004-12-04T05:21:58
   Editor: GiannyDamour <gd...@apache.org>
   Wiki: Apache Geronimo Wiki
   Page: Working with Enterprise JavaBeans
   URL: http://wiki.apache.org/geronimo/Working with Enterprise JavaBeans

   Some layout problems...

Change Log:

------------------------------------------------------------------------------
@@ -102,8 +102,8 @@
 
 The configuration of such a relationship requires the mapping of one and only one CMR field of the two 
 related entity beans. The identification of the mapped CMR field is achieved via the ''relationship-role-source''
- and ''cmr-field'' elements. The mapping ''per se'' is provided via the ''role-mapping'' element. This latter 
-is a collection of ''cmr-field-mapping'' elements specifying the mapping between the columns of the two tables
+and ''cmr-field'' elements. The mapping ''per se'' is provided via the ''role-mapping'' element. This latter is
+a collection of ''cmr-field-mapping'' elements specifying the mapping between the columns of the two tables
 associated to the related entity beans. More accurately, its ''key-column'' sub-element identifies a column 
 associated to a CMP field of the source entity bean. Note that this CMP field must store either the primary 
 key or, in the case of compound primary keys, a part of it. The ''foreign-key-column'' sub-element indicates 
@@ -198,9 +198,7 @@
 === CMP with Unknown Primary Key ===
 
 The set-up of entity beans with unknown primary key classes requires the configuration of:
-  * additional CMP fields. These fields, exclusively used to hold the (auto-generated) primary keys, must 
-use the ''cmp-field-class'' optional element. This element specifies the full class name of additional 
-CMP fields, as this information can not be derived from the entity bean class; and
+  * additional CMP fields. These fields, exclusively used to hold the (auto-generated) primary keys, must use the ''cmp-field-class'' optional element. This element specifies the full class name of additional CMP fields, as this information can not be derived from the entity bean class; and
   * primary key generators for these additional fields.
 
 == Flushing Strategy ==
@@ -214,7 +212,6 @@
 
 Users are invited to identify hereafter the databases and their associated drivers, which have been 
 used successfully with the CMP engine:
-  * Oracle9i with Oracle10g JDBC driver. Note that Oracle10g is backward compatible and supports know 
-properly the ''Prepared''''''Statement.set''''''Binary''''''Stream()'' method.
+  * Oracle9i with Oracle10g JDBC driver. Note that Oracle10g is backward compatible and supports now properly the ''Prepared''''''Statement.set''''''Binary''''''Stream()'' method, which is used for the storage of Dependent Value Classes.
 
 ''Nota bene'': the implementation requires a JDBC 3.0 compliant driver.