pojo data persistence

pojo data persistence
pojo pojo pojo
pojo data persistence  
  CocoBase PURE POJO

features of new v5.0
> pure pojo - ejb3
> magic mapper
> high performance
> o/r mapping
> querying solutions
> cocobase is free
> eclipse, spring
> technical spec's

  tech support


EJB 3.0 JPA Gets Enterprise Data Persistence Functionality With CocoBase Implementation

New CocoBase PURE POJO Version 5.0 SR1 Provides Tightly Integrated Commercial Support for the EJB 3.0 JPA Specification.

Developers Can Now Take Advantage Of The High Performance Enterprise-Focused Dynamic O/R Mapping Technology of CocoBase To Create Success In Their EJB 3 JPA based Corporate Applications.

CocoBase® Enterprise O/R



The Enterprise JavaBeans (EJB) 3.0 specification includes an additional persistence specification called the Java Persistence API (JPA). It is an API for creating, removing and querying across lightweight Java objects and can be used both within a compliant EJB 3.0 Container and a standard Java SE 5 environment.


CocoBase PURE POJO version 5.0 is the award winning industry leader for Enterprise Object to Relational Mapping (ORM) Tools shipping since early 1997.  It was the first 100% based Java O/R Mapping tool and continues to lead the industry with technological innovations providing developers the most full featured and easy to use tool for persisting data in enterprise-level Java applications.  The new 5.0 service release 1 of CocoBase PURE POJO is focused on providing support for the EJB 3.0 Java Persistence API (JPA). 

The JPA is now the standard for programming data persistence on the J2EE and J2SE platforms.  With this release of version 5.0 Service Release 1, corporate applications built with the JPA can easily utilize the powerful enterprise-level Dynamic O/R Mapping architecture of CocoBase to manage the persistence of data for their companies.

CocoBase offers a number of key advantages for developers programming with the EJB 3.0 JPA that are not available with JPA implementations from other key ORM tools;

1) Includes the highly intuitive and advanced CocoBase GUI’s designed specifically for ease of use and high productivity. CocoBase is the only major ORM tool to include any kind of comprehensive GUI for building EJB 3 persistence.

2) Provides an advanced enterprise-focused commercial persistence technology and platform that the JPA API’s are integral part of.  This allows the developer to make use of the basic features supported in the JPA as well as the extensive additional persistence functionality and mapping and runtime features of CocoBase. The patented CocoBase Dynamic O/R Mapping architecture was designed from the beginning to easily manage the full range of persistence requirements from simple to complex.

3) Provides an extreme high performance and scalable persistence solution.  The CocoBase Persistence Manager is designed such that applications run up to 2 to 3 times faster than the same calls with just a JDBC driver. This high performance along with the linear scalability characteristics of CocoBase insures that applications easily meet usability expectations and cut the costs or need of additional software or hardware.

4) Provides the only major commercial (non open-source) ORM tool implementation of the EJB 3.0 JPA. This allows corporate applications to take advantage of a patented and source-code protected code base. The CocoBase JPA solution is an integral part of the toolset that was designed tightly and cohesively by the same engineering team that built the tool from the beginning.  The result takes full advantage of the decade old mature and stable persistence technology that is a key requirement for use in mission critical corporate applications.



CocoBase PURE POJO version 5.0 Service Release 1 includes an implementation of the Java Persistence API, or simply JPA, which is part of the Enterprise Java Beans specification (JSR-220 FR) version 3. JPA is the specification of the Java API for the management of persistence and object/relational mapping within Java EE (enterprise edition) and Java SE (standard edition), which means JPA applications are no longer restricted to EJBs running within a Java EE container, but can also be executed as regular standalone or rich client Java applications. The complete specification can be found at:


The CocoBase version 5 system includes a GUI Workbench and multiple Runtime Persistence Managers.  One Persistence Manager is our native CocoBase PersistenceManager which closely resembles the EJB3 Persistence Manager, but is not constrained to run on the Java5 platform.  Another Persistence Manager is our JPA compatible Persistence Manager that is designed for the both the J2EE and J2SE Java5 platforms. The Native CocoBase API is a plug-able Facade pattern that’s quite similar to the JPA API, and it even includes compatibility layers to previous versions of the CocoBase APIs.  As a result of this architecture, CocoBase can add new standard API compatibility support such as EJB3 without a system re-architecture effort.  Both editions share the same underlying implementation, codebase and enterprise capabilities.

The runtime is currently compatible with the Annotation Mapping and the CocoBase XML Repository format used by the CocoBase 5 workbench.  The EJB3 XML format support hasn’t yet been provided as part of this implementation – that support is planned to be released soon.

The current CocoBase 5 Service Release 1 edition Workbench only supports POJO java classes.  It also currently supports only the CocoBase 5 XML Repository format, and not the EJB3 Native XML format.  This means that if the developer wishes to use the CocoBase GUI to generate their Java classes, the tool will generate only POJO classes, and not annotated java classes in this release.  Also, there’s no export yet for the EJB3 Native XML support, nor is their support yet for that XML format in the EJB3 API.  Both the annotation class support and native EJB3 XML repository support are planned to be released soon.

Because the EJB3 API supports the use of the CocoBase Repository format, it also supports many extended mapping features not available in other EJB3 implementations.  This includes custom SQL for all crud operations, the support of stored procedures as replacement for crud operations, and other advanced mapping facilities included out of the Box in the workbench.

Getting Started With CocoBase for EJB 3.0 JPA Development

CocoBase PURE POJO version 5.0 Service Release is available for download from the company website at any time by simply requesting a download of the tool.  The tool has documentation and examples linked off of the Help section in the workbench.  This includes basic instructions, and will refer the developer to the large set of EJB3 JPA examples included out of the box with the distribution.  This just takes a few minutes and you can have CocoBase downloaded to your computer and installed.  There is a Getting Started document for JPA development that quickly facilitates the developer to start development.  There are also additional user guides and assistance to help the developer to get started developing with CocoBase.  At any time the developer may contact the CocoBase engineering team for technical support by emailing to support@thoughtinc.com.


This document is copyrighted and owned solely by THOUGHT Inc.® 2006. CocoBase® and THOUGHT Inc.® are registered trademarks of THOUGHT Inc.®. Dynamic POJO Data Persistence™, Dynamic O/R Mapping™, Dynamic Object to Relational Mapping™, Dynamic Universal Querying™ and Dynamic Transparent Persistence™ are pending trademarks of THOUGHT Inc.®. CocoBase® technology is based on US patent #5857197 as well as additional pending patents directed to object navigation, object modeling, querying and caching. All other trademarks are property of their respective company. This publication is provided "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement, to also include any and all technical inaccuracies or typographical errors.