OpenEdit Developer ForumWelcome to the OpenEdit User Forum. You must be registered and logged in to post a new comment or topic. This forum is only for developers who want to discuss the technical aspects of the OpenEdit Framework. For end user technical support please visit the EnterMedia web site. OEF Database PersistenceHi Java Developers, Does anyone have opinions about the OpenEdit Framework using Apache OpenJPA for databases? OEF already has a simple Hibernate plugin but it has some problems. First major problem is that Hibernate uses static factory classes and that means we can only have one database connection per web application. This is no good since OpenEdit supports multiple catalogs per webapp. We expect that each catalog can be mapped to it's own database tables. Second problem is that Hibernate depends on transactions to be opened and closed for each web request. In our objects we do not rollback very often. Even an incomplete transaction is usually better than not saving anything at all. Here is a nice overview of OpenJPA. Am going to see if we can get it working this week. Posted by Christopher Burkey Sun, Nov 16 2008 9:18 PM
|
Most Recent Posts
encodings ...
(4 comments)
Slamdance
(7 comments)
Help upgrading jars on starter war
(6 comments)
Help, Velocity Generator not initializing
(4 comments)
Multiple Main Sites
(10 comments)
Search filtering by theme
(3 comments)
xml version "s1.0" error
(4 comments)
How can i localization the openedit?
(3 comments)
Problem with the interface
(4 comments)
latest openedit-editor build
(2 comments) Archive
Log in
Syndicate:
|
Copyright 2008 OpenEdit Inc. All rights reserved. last modified: Nov 16 2008

I'm a big fan of Database for Objects (www.db4o.com) - some of the JPA solutions (such as JPOX) http://www.jpox.org/docs/1_2/developer/db4o.html use Db4o to simplify the storage sytem. The ability to store entire object graphs with a single call and then search without any changes to the objects/classes themselves is pretty amazing. Relationships aren't much of a problem since you no longer have to create any kind of object -> backend mapping - it's all just objects.