The IBM Rational Development Tools for OSGi Applications help you build enterprise applications that benefit from the modularity, dynamism, versioning, and third-party library integration provided by the OSGi applications framework.
The OSGi framework is a dynamic component model that is growing in popularity within enterprise architectures. The IBM® WebSphere® Application Server V7 Feature Pack for OSGi Applications and Java™ Persistence API (JPA) 2.0 was delivered for use with WebSphere Application Server V7.0 with Fix Pack 9 and above. This article describes the steps involved in converting a Java EE Web application that uses JPA 1.0 to an OSGi application that uses features in JPA 2.0 plus Blueprint injection of objects. Sample code for a simple WebSphere Application Server application is included for illustrative purposes.
By Kevin Sutter, IBM® WebSphere® Application Server provides a complete JPA solution based on the Apache OpenJPA project. Although the use of alternate JPA providers, such as Hibernate JPA, is doable, the question remains: "why?" This article explains why the continued use of the WebSphere JPA solution always makes the most sense.
The IBM WebSphere Application Server V7 Feature Pack for OSGi Applications and Java Persistence API 2.0 is now GA & enables productivity through a simplified component model and delivers enhanced performance through new relational database access standards.
How the Criteria API builds dynamic queries and reduces run-time failures
Pinaki Poddar (firstname.lastname@example.org), Senior Software Engineer, IBM
Summary: A query for persistent Java™ objects is typesafe if a compiler can verify it for syntactic correctness. Version 2.0 of the Java Persistence API (JPA) introduces the Criteria API, which brings the power of typesafe queries to Java applications for the first time and provides a mechanism for constructing queries dynamically at run time. This article describes how to write dynamic, typesafe queries using the Criteria API and the closely associated Metamodel API.
As the JPA Expert Group (JSR-317) nears completion of the JPA 2.0 specification, this article introduces you to some of the new concepts and features in this updated specification. It also explains how you can experience this new functionality with the Apache OpenJPA project, an open-source, robust, high performance, scalable implementation of the JPA specification.
The JPA 2.0 Open Alpha has ended and is now included in this Feature Pack Open Beta. Please click the link above to access this new Beta, including code, documentation, and forum support.
Object-relational persistence is a key developer requirement for many application developer scenarios. JPA is the Java EE standard for object-relational persistence and was first introduced as part of Java EE 5. As part of the Java EE 6 standards, JPA 2.0 (JSR-317) updates object-relational capabilities with important developer APIs and enhancements.
Key additions in JPA 2.0 include:
Significant programmer productivity improvements
Innovative APIs from Open Source (standardized)
Extended query language
Welcome to Apache OpenJPA
Apache OpenJPA is a Java persistence project at The Apache Software Foundation that can be used as a stand-alone POJO persistence layer or integrated into any Java EE compliant container and many other lightweight frameworks, such as Tomcat and Spring.
The 1.x releases (1.2.2 is the latest) are a feature-rich, compliant implementation of the Java Persistence API (JPA) 1.0 part of the JSR-220 Enterprise Java Beans 3.0 specification, which pass the Sun JPA 1.0b Technology Compatibility Kit.
The upcoming 2.0 release (see JPA 2.0 Roadmap) implements the JSR-317 Java Persistence 2.0 specification, which is backwards compatible to the JPA 1.0 specification.