JPA driver and JPA module for OpenCms - professional opensource CMS (Content Management System)
Be the first to post a text review of JPA driver for OpenCms. Rate and review a project by clicking thumbs up or thumbs down in the right column.
2009-04-10 * downgrade to OpenJPA 1.2.0 due problems with HSQLDB * added status.txt for performed tests on different databases * fixed some problems with installation on DB2 and Oracle 2009-03-31 * update OpenJPA to version 1.2.1 * enable OpenJPA query cache by default * enable prepared statement pooling by default in DBCP configuration 2009-02-16 * fixed installer for schema generation for Firebird, Interbase and Sybase * added JDBC driver for Firebird * the query C_READ_RESOURCE_OUS is rewritten to be compatible with more databases branch 7.0.5 * add drop table statements for drop table script in the setup/databases folder 2008-10-11 * fixed create table script for Apache Derby. All binary filed are of type BLOB * changed collate for MS SQL Server to be case insensitive table names according to SQL standard collate is changed to SQL_Latin1_General_CP1_CI_AS * Added testing configuration folder for Apache Derby * removed config.jpa folder for tests. In case you want to test against database with JPA driver, which has already has configuration folder, just change managers to be from org.opencms.db.jpa package Example: db.vfs.driver=org.opencms.db.postgresql.CmsVfsDriver db.vfs.pool=opencms:default db.vfs.sqlmanager=org.opencms.db.postgresql.CmsSqlManager db.project.driver=org.opencms.db.postgresql.CmsProjectDriver db.project.pool=opencms:default db.project.sqlmanager=org.opencms.db.postgresql.CmsSqlManager db.user.driver=org.opencms.db.postgresql.CmsUserDriver db.user.pool=opencms:default db.user.sqlmanager=org.opencms.db.postgresql.CmsSqlManager db.history.driver=org.opencms.db.postgresql.CmsHistoryDriver db.history.pool=opencms:default db.history.sqlmanager=org.opencms.db.postgresql.CmsSqlManager should be changed to db.vfs.driver=org.opencms.db.jpa.CmsVfsDriver db.vfs.pool=opencms:default db.vfs.sqlmanager=org.opencms.db.jpa.CmsSqlManager db.project.driver=org.opencms.db.jpa.CmsProjectDriver db.project.pool=opencms:default db.project.sqlmanager=org.opencms.db.jpa.CmsSqlManager db.user.driver=org.opencms.db.jpa.CmsUserDriver db.user.pool=opencms:default db.user.sqlmanager=org.opencms.db.jpa.CmsSqlManager db.history.driver=org.opencms.db.jpa.CmsHistoryDriver db.history.pool=opencms:default db.history.sqlmanager=org.opencms.db.jpa.CmsSqlManager In case the database has not test configuration folder, just copy existing one and adjust required values. If this database has not create table script just enable schema generation from OpenJPA or export schema from existing OpenCms instalation and contribute this script to the project. * added single-unittests unit task to be able to excute single package test from ant. To do that, do the following ( example is with the file package test): $ ant clean $ ant bindist $ ant single-unittests -Dtest=file 2008-10-03 Fixed bugs * fixing bug, preventing user to use JPA driver for databases which has SQL driver support New Features and improvements * added full list of supported databases/RDBMS from Apache OpenJPA Apache Derby Borland Interbase Borland JDataStore DB2 - spoorted by SQL driver already Empress Firebird H2 Database Engine Hypersonic Database Engine & HSQLDB - spoorted by SQL driver already Informix Dynamic Server InterSystems Cache Microsoft Access Microsoft SQL Server - spoorted by SQL driver already Microsoft Visual FoxPro MySQL - spoorted by SQL driver already Oracle - spoorted by SQL driver already Pointbase PostgreSQL - spoorted by SQL driver already Sybase Adaptive Server Enterprise * the test configuration data is already included example for testing JPA driver with PostgreSQL * database schema was converted for Apache Derby, Borland Interbase, Firebird, Sybase with Apache DDLUtils, but installation fails for Apache Derby and Firebird. The database generation is doing from OpenJPA for these databases instead of existing scripts by default. Known limitations * in case the installation is stopped during importing modules phase, the peristence.xml file should be restored from distribution before restarting of installation * junit tests fail with data cache less than 2000 objects and/or switched on query data cache Status * the installer is not tested for Borland Interbase, Borland JdataStore, Empress, Informix Dynamic Server, InterSystems Cache , Microsoft Access, Microsoft Visual FoxPro, Pointbase,Sybase Adaptive Server Enterprise 2008-09-02 Features & Improvements * initial update of OpenCms installer for JPA support * addedpooling for EntityManager's instances * the functionality of opencms-jpa module is implemented in org.opencms.db.jpa.CmsSqlManager Status * the JPA driver pass all file junit tests * quality of the installer patch is still alpha
Be the first person to add a text review.
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: