JPOX
JPOX
 Project  |  Ver 1.1  |  Ver 1.2  |  JDO  |  JPA  |  Guides  |  Tools
Overview
Support
Development
Why JPOX ?

Choosing a Java Persistence mechanism will come down to your requirements in terms of cost, functionality, support, etc.

  • JPOX is an Open Source implementation, meaning that you have full access to the source code for all versions of JPOX. With this you have the capability to correct any errors that you encounter, but also better understand the JDO/JPA process, and you can potentially extend JPOX to suit your needs.
  • JPOX is free. Our license is the Apache 2 license, providing the code and executables (JARs) free of charge. You are free to use JPOX in your projects. Please refer to the license for the precise wording. JPOX will remain Open Source. JPOX isn't owned by a company who can change the license to suit their own corporate needs, we are individual volunteers who provide our time to write a quality implementation.
  • The JPOX license (Apache 2) is very flexible, much more than the license used for some other notable object/relational mapping software which use the LGPL.
  • JPOX implements all JDO specifications (1.0, 2.0, 2.1) and all JPA specifications (1.0), providing all mandatory items and the majority of optional items as well as providing several value-added extensions.
  • JPOX passes the JDO1, JDO2, JDO2.1, and JPA1 TCKs, meaning that it meets the JDO1, JDO2, JDO2.1 and JPA1 standards and can be used interchangeably with other certified implementations
  • JPOX supports persistence to the vast majority of RDBMS databases on the market today. We are always updating our support to match new releases of existing databases, or to add new databases when they appear. JPOX 1.2 supports persistence to the DB4O object datastore. We aim to support other types of datastores in the future.
  • JPOX provides outstanding performance when compared with the competing technologies (which themselves use terms like "ultra-high performance" for their own capabilities, hence we ran out of superlatives for JPOX so just leave it to users to judge for themselves rather than listen to meaningless rhetoric).
  • JPOX does not bring in large numbers of dependencies unlike other persistence frameworks (in particular Hibernate) that have to provide a zip file just to package all of their requirements up. In fact JPOX could be run with just 2 third-party libraries - as lightweight as you can get!
  • JPOX is quality-driven being developed using a Test Driven Development methodology. We have more than 1000 unit tests that are run before any release guaranteeing a stable product. In addition we baseline our capabilities against the JDO and JPA TCKs - the definition of specification compliance.
  • JPOX provides a level of free support by way of an online forum. Users can ask questions, exchange code samples and help each other. We can't guarantee immediate responses but we typically provide a fast service. If the developers of JPOX can't help you immediately, there are usually other contributors or users who can help out. Our web site provides extensive documentation to help out in the majority of areas. In addition, if you wish a more permanent and reliable support, you can make a donation to the project and we will provide support to match.
  • JPOX support and training can be arranged with the developers of JPOX.
  • JPOX is open to contributions/donations allowing individuals to help out and allowing companies to sponsor features that they require for their deployments of JPOX.
  • JPOX is plugin-driven using the OSGi standard mechanism, providing plugins to external caching software (Tangosol, EHCache, OSCache, SwarmCache), to external database-pooling software (DBCP, C3P0), as well as frameworks such as SpringFramework.