db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject cvs commit: db-ojb/forrest/src/documentation/content/xdocs/docu pb-tutorial.xml sequencemanager.xml
Date Mon, 26 Apr 2004 23:34:43 GMT
arminw      2004/04/26 16:34:43

  Modified:    forrest/src/documentation/content/xdocs site.xml
               forrest/src/documentation/content/xdocs/docu pb-tutorial.xml
  Added:       forrest/src/documentation/content/xdocs references.xml
  adapted file + update
  Revision  Changes    Path
  1.5       +9 -2      db-ojb/forrest/src/documentation/content/xdocs/site.xml
  Index: site.xml
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/site.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- site.xml	26 Apr 2004 18:25:21 -0000	1.4
  +++ site.xml	26 Apr 2004 23:34:43 -0000	1.5
  @@ -76,7 +76,7 @@
           <tutorials label="Tutorials">
               <mapping-tutorial label="Mapping Tutorial" href="mapping-tutorial.html"
description="Mapping tutorial">
  -                <metadata href="#metadata"/>
  +                <metadata-mapping href="#metadata"/>
               <pb-tutorial label="The PB API" href="pb-tutorial.html" description="PB
               <odmg-tutorial label="The ODMG API" href="odmg-tutorial.html" description="odmg
  @@ -211,6 +211,7 @@
               <tomcat href="tomcat/"/>
               <commons-logging href="commons/logging/"/>
               <jcs href="http://jakarta.apache.org/turbine/jcs/index.html"/>
  +            <jetspeed-2 href="http://portals.apache.org/jetspeed-2/"/>
           <log4j href="http://logging.apache.org/log4j/"/>
           <ant href="http://ant.apache.org/"/>
  @@ -230,6 +231,7 @@
           <tangosol-blog href="http://www.freeroller.net/page/jmckerr"/>
           <javagroups href="http://www.jgroups.org/javagroupsnew/docs/index.html"/>
  +        <ambysoft href="http://www.ambysoft.com/mappingObjects.html"/>
           <axgen href=""/>
           <sun href="http://java.sun.com/">
               <jdo href="products/jdo/">
  @@ -238,6 +240,11 @@
           <odmg-group href="http://www.odmg.org/"/>
           <junit href="http://www.junit.org"/>
  +        <tammi href="http://tammi.sourceforge.net/"/>
  +        <ojbc href="http://ojbc.sourceforge.net/"/>
  +        <intact href="http://www.ebi.ac.uk/intact/"/>
  +        <nees href="http://www.nees.org/"/>
  +        <ojb-net href="http://ojb-net.sourceforge.net/"/>
  1.1                  db-ojb/forrest/src/documentation/content/xdocs/references.xml
  Index: references.xml
  <?xml version="1.0" encoding="UTF-8"?>
    Copyright 2002-2004 The Apache Software Foundation
    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
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    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.
  <!-- @version $Id: references.xml,v 1.1 2004/04/26 23:34:43 arminw Exp $ -->
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
          <title>OJB - References and Testimonials</title>
              <person name="Thomas Mahler" email="thma@apache.org"/>
              <title>References and Testimonials</title>
                  <title>projects using OJB</title>
                          <link href="ext:jetspeed-2">Jakarta JetSpeed</link>
                      Jetspeed is an Open Source implementation of an
                      Enterprise Information Portal, using Java and XML.
                      OJB will be the default persistence model within Jetspeed 2.
                          <link href="ext:tammi">The Tammi project</link>
                      Tammi is a JMX-based Java application development framework and
                      run-time environment providing a service architecture for J2EE server
                      side Internet applications that are accessible from any device that
                      supports HTTP including mobile (wireless) handsets.
                      Future plans include integration of Apache OJB based persistence
                      services to the framework.
                          <link href="ext:ojbc">The Object Console project</link>
                      The Object Console is an open web based application meant for the administration
                      of objects via the web. Any object that is persistable by the
                      ObJectRelationalBridge (OJB) framework can be managed through this tool.
                      In addition, this tool provides administration functionality for the
                      ObJectRelationalBridge (OJB) framework itself.
                      Object Console uses Struts and OJB. It ships with full sourcecode and
                      is thus a great source for learning Struts + OJB techniques.
                          <link href="ext:intact">The IntAct project</link>
                      The IntAct project establishes a knowledgebase for protein-protein interaction
                      It's hosted at EBI - European Bioinformatics Institute, Cambridge.
                      IntAct uses OJB as its persistence layer.
                          <link href="ext:nees">Network for Earthquake Engineering Simulation</link>
                      The NEES program will provide an unprecedented infrastructure
                      for research and education, consisting of networked and geographically
                      distributed resources for experimentation, computation, model-based
                      data management, and communication.
                      OJB is used as the O/R mapping layer.
                          <link href="ext:ojb-net">The OJB.NET project</link>
                      OJB.NET is an object-to-relational persistence tool for the .NET platform.
                      It enables applications to transparently store and retrieve .NET objects
                      using relational databases.
                      OJB.NET is a port ojb Apache OJB to the .NET platform
                          <link href="http://www.openemed.org/">The OpenEMed project</link>
                      OpenEMed is a set of distributed healthcare information service
                      components built around the OMG distributed object specifications
                      and the HL7 (and other) data standards and is written in Java for
                      platform portability.
                      OpenEMed uses ODMG as its persistence API.
                      OJB is used as ODMG compliant O/R tool.
                  <strong><link href="http://sourceforge.net/projects/anemone/">The
Anemone project
                  Anemone is a collaborative learning web application built using 100% Java
                  such as Tapestry, OJB, EJB and JAAS.
                  <strong><link href="http://sourceforge.net/projects/opencmsfacade/">The
Facade project
                  Facade add and additional model 2 framework to OpenCms (http://www.opencms.org)
                  similar to struts. This project also includes a sub-project that provides
an api to
                  Object Relational Bridge.
                  Facade OJBI interfaces to the OJB persistence layer.
                  <title>user testimonials
                      "We're using OJB in two production applications at the Northwest Alliance
                      for Computational Science and Engineering (NACSE).  One is a data mining
                      toolset, and the other is a massive National Science Foundation project
                      that involves huge amounts of data, and about 20 or 25 universities
                      research groups like mine.
                      In fact, I've begun making OJB sort of a de-facto standard for NACSE
                      java/database development.  I've thrown out EJB's for the most part
                      I've tried JDO from Castor, but I'm sticking with OJB. Maybe we'll
                      reconsider JDO when the OJB implementation is more complete."
                      "We are planning a November 2003 production deployment with OJB and
                      IT!!  We have been in development on a very data-centric application
in the
                      power industry for about 5 months now and OJB has undoubtedly saved
                      countless hours of development time.  We have received benefits in the
                      following areas:
                      -> Easily adapts to any data model that we've thrown at it.  No problems
                      mapping tables with compound keys, tables mapping polymorphic relationships,
                      identity columns, etc.
                      -> Seemlesly switches between target DB platforms.  We develop and
unit test
                      on our local workstations with HSQLDB and PostgreSQL, and deploy to
                      using the Type 4 JDBC driver from IBM.  Works great!
                      -> Makes querying a breeze with the PersistenceBroker API
                      Overall we have found OJB to be very stable (and we've really tested
it out
                      quite a bit).  The only issues we've got outstanding at the moment is
                      support for connections to multiple databases, but I've noticed in CVS
                      the OJB guys are already fixing this for OJB 0.9.9."
                      "We've been using it in "production" for a long time now, from about
                      version 0.9.4, I believe.  It has been very robust.  We don't use all
                      its features.   We've only see to failures of our persistent store in
                      about 9 months, and I'm not sure they were due to OJB."
                      "So yes, we have made a quite useful mediumsized production website
                      based on OJB (with JBoss, Jakarta Jetspeed, Jakarta Turbine
                      and Jakarta Jelly, three Tomcats, OpenSymhony OSCache and for
                      the database MSSQL server, all running on Win2000.)
                      It is attracting between 600 and 9000 (peak) users a day,
                      and runs smoothly for extended periods of time.
                      And no, I can not actually show you the wonders of the editorial
                      interface of the content management system, because it is
                      hidden behind a firewall.
                      I feel OJB is quite useful in production, but you certainly
                      have to know what you are doing and what you are trying
                      to achieve with it. And there have been some tricky aspects,
                      but these could be solved by simple workarounds and small hacks.
                      The main thing about OJB is that AFAIK it has an overall clean
                      design, and it far beats making your own database abstraction
                      layer and object/relational mapper. We certainly do not use all
                      of it, only the Persistence Broker parts, so there was less to
                      learn. We love the virtual proxy and collection proxy concepts,
                      the criteria objects for building queries, and the nice little
                      hidden features that you find when you start to learn the system."
                      "My Company is building medium to large scale, mission critical
                      applications (100 - 5.000 concurrent users) for our customers.
                      Our largest customer is KarstadtQuelle, Europes largest retail company.
                      The next big system that will go in production (in June) is the new
                      logistics system for the stationary logistics of Karstadt.
                      Of course we are using OJB in those Systems!
                      We have several OJB based systems now in production for over a year.
                      We never had any OJB related problems in production.
                      Most problems we faced during development were related to the
                      learning curve developers had to face who were new to O/R mapping."
                      "I've also worked with OJB on high-load situations in J2EE environments.
                      We're using JRun and/or Orion with OJB in a clustered/distributed
                      environment. This is a National Science Foundation project called the
                      Network for Earthquake Engineering Simulation (NEES).
                      The only major problem that we ran into was the cache.  JCS just isn't
                      good, and hasn't seemed to get much better over the last year.  We ended
                      up plugging in Tangosol's Coherence Clustered Cache into the system.
                      can also do write-behinds, and buffered data caching that is queued
                      transaction.  That's important to us because we're dealing with very
                      expensive scientific data that _can't_ get lost if a db goes down. Some
                      of these Tsunami experiments can get pretty expensive.
                      Otherwise, we use mostly the PersistenceBroker, and a little of the
                      ODMG.  Performance seems better on PB, but less functional.  It's not
                      really that much of a problem anyway, because we can cheaply and quickly
                      add app-servers to the cluster."
  1.3       +2 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/pb-tutorial.xml
  Index: pb-tutorial.xml
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/pb-tutorial.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- pb-tutorial.xml	26 Apr 2004 18:25:20 -0000	1.2
  +++ pb-tutorial.xml	26 Apr 2004 23:34:43 -0000	1.3
  @@ -163,7 +163,7 @@
                       unique id. This automatic assignment of unique Ids for the attribute
                       <code>id</code> has been explicitly declared in the
                       <link href="site:repository">XML repository</link> file,
as we discussed in the
  -                    <link href="site:mapping-tutorial/metadata"></link>.
  +                    <link href="site:mapping-tutorial/metadata-mapping"></link>.
                       If several objects need to be stored, this can be done within
  1.2       +2 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/sequencemanager.xml
  Index: sequencemanager.xml
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/sequencemanager.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- sequencemanager.xml	26 Apr 2004 18:25:20 -0000	1.1
  +++ sequencemanager.xml	26 Apr 2004 23:34:43 -0000	1.2
  @@ -189,7 +189,7 @@
                           Per default OJB internally uses a High/Low algorithm based sequence
                           for the generation of unique ids, as described in
  -                        <link href="http://www.ambysoft.com/mappingObjects.html">
  +                        <link href="ext:ambysoft">
                               Mapping Objects To Relational Databases</link>.
                           This implementation is called

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

View raw message