User: fleury  
  Date: 00/11/16 18:11:53

  Modified:    developers jboss-jaws.html
  Log:
  jaws updated
  
  Revision  Changes    Path
  1.4       +27 -2     newsite/developers/jboss-jaws.html
  
  Index: jboss-jaws.html
  ===================================================================
  RCS file: /products/cvs/ejboss/newsite/developers/jboss-jaws.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- jboss-jaws.html   2000/11/14 06:07:55     1.3
  +++ jboss-jaws.html   2000/11/17 02:11:52     1.4
  @@ -19,10 +19,35 @@
                                                </tr>
                                                <tr>
                                                        <td class="newsbody"><font 
face="Arial,Helvetica,sans-serif"><img src="../pictures/jaws.jpg"><br>
  -                                                             The Minerva JDBC 
connection pooling module has been added to the codebase, thanks to Aaron Mulder. This 
module complements JAWS by adding a pluggable connection pooling mechanism.</font>
  -                                                             <p><a 
href="../minerva/index.html"><font face="Arial,Helvetica,sans-serif">View the Minerva 
JavaDocs</font></a></p>
  +            The Minerva JDBC connection pooling module has been added to the 
codebase, 
  +            thanks to Aaron Mulder. This module complements JAWS by adding a 
pluggable 
  +            connection pooling mechanism. 
  +            <p>During development of jBoss/Server version 1.0 (then known as 
EJBoss), 
  +              our team recognized the need for an object-to-relational (O-R) 
mapping 
  +              tool. Enter JAWS, the acronym for "Just Another Web Storage," an 
  +              API for mapping Enterprise JavaBeans objects to relational database 
  +              persistent stores. The jBoss/JAWS project has since taken on a life 
  +              of its own. That's because we are not only maintaining and enhancing 
  +              the original code base that defined a simple, yet proprietary O-R 
  +              mapping tool, we are now also extending the product to support the 
  +              popular third-party O-R mapping tools being employed by some 
jBoss/Server 
  +              users. That means there's plenty of work to do, so you can join 
  +              the jBoss/JAWS project and contribute to the coolest O-R mapping 
  +              open source project around. We encourage you to view the jBoss/JAWS 
  +              mail archives. </p></font>
  +            <p>&nbsp;</p>
  +            <p><a href="../minerva/index.html"><font 
face="Arial,Helvetica,sans-serif">View 
  +              the Minerva JavaDocs</font></a></p>
                                                                <p><font face="Myriad 
Web,Arial">Get a feature list of the project as a whole&nbsp;(under 
construction)</font></p>
                                                                <p></td>
  +                                             </tr>
  +                                             <tr>
  +                                                     <td class="newsheader"><b>What 
is O/R Mapping?</b></td>
  +                                             </tr>
  +                                             <tr>
  +                                                     <td class="newsbody">O-R 
mapping technology grew out of the differences between how object-oriented languages 
represent objects in memory and how relational databases store data on disk. Objects 
in the Java language might contain only primitive data types such as int, double, and 
very simple aggregate objects such as String, making it very easy to express the 
object's layout on disk. In the case of storing such a simple object in a flat disk 
file, you would just write each primitive data type variable and each String object in 
their string form sequentially into the flat file. As you can imagine, reading such 
objects back from disk into a memory-based object would be just as easy. However, what 
about storing more complex objects such as those that contain other objects that 
contain yet other objects? And what about storing both simple and complex objects into 
relational databases?<p>
  +
  +Of course the more complex the object that must be stored to disk, the more 
intelligent the O-R mapping tool must be. An O-R mapping tool must understand how to 
traverse the complex object's memory graph and figure out how to store it to and read 
it from disk. To add to the complexity, the graph of a single object might contain 
multiple objects that each reference a single, unique object, and it could also 
contain objects that recursively reference themselves or the original object. In these 
cases the O-R mapping tool would have to avoid persisting the same object multiple 
times, perhaps even ending up in an endless loop because of the self-referencing 
composition! On the other hand, all complex Java objects finally boil down to 
variables of primitive data types and those of class String. Therefore, while it can 
be quite challenging to persist very complex objects, it is not
                                                </tr>
                                                <tr>
                                                        <td 
class="newsheader"><b>Features</b></td>
  
  
  

Reply via email to