Wednesday, June 24, 2009

EclipseLink in Galileo: Persistence at your fingertips

The Eclipse Galileo release signifies another important milestone for the EclipseLink project. The Galileo release makes EclipseLink 1.1.2 available and easier to use for the entire Eclipse community. Developers using the Java EE or Modeling Tools distributions of the Eclipse IDE will find EclipseLink included and available for use in Equinox OSGi, RCP, EMF, Java EE, and Java SE applications.

The EclipseLink 1.1.2 release includes a comprehensive set of persistence services:

  • EclipseLink JPA: Java Persistence API support for object-relational mapping with many advanced mapping, performance, and scalability features targeting Java EE, Java SE, and OSGi usage with Equinox specific extensions.
  • EclipseLink MOXy: Object-XML Binding (JAXB) support including advanced mappings, meet-in-the middle mapping without annotations, and pluggable parser support for optimal performance.
  • EclipseLink SDO: Service Data Objects 2.1.1 reference implementation including a Data Access solution for integrating JPA entities with SDO.
  • EclipseLink DBWS: Database Web Services solution enabling the generation of JAX-WS services based on relational metadata harnessing EclipseLink's JPA and MOXy capabilities.

EclipseLink for Java Developers

EclipseLink's inclusion in the Eclipse IDE for Java EE Developers combined with the extended support in WTP's Dali Java Persistence Tools project allows developers to start building JPA enabled applications quickly and easily. The Dali integration allows developers to optionally select EclipseLink as their JPA implementation and have it automatically added to their project classpath. This support along with Dali's rich validation and intelligent code assist provide a highly productive environment for developing, testing, packaging, and deploying JPA enabled applications.

EclipseLink for Modeling

The Eclipse Modeling Tools package of the Eclipse IDE includes the EclipseLink JPA feature and Teneo's EMF/EclipseLink integration. Teneo's EclipseLink support provides tools to generate JPA mappings from an EMF model or simply map their EMF models to a relational database. It also extends EclipseLink JPA with transparent runtime support for persisting EMF models. This out-of-the-box support for JPA persistence for EMF models will simplify the development of RCP and Equinox applications that leverage relational databases.

EclipseLink for RT

The EclipseLink project is also available as part of the Galileo update site under the EclipseRT Target Platform Components allowing developers to leverage P2 for provisioning of their Equinox (OSGi) environments. The provisioning allows developers to select the persistence services they require; JPA for object-relational, MOXy for Object-XML binding, or SDO for Service Data Object usage and have the necessary bundles downloaded and setup in their target platform environment.

Please download Galileo and try out the new EclipseLink capabilities. Provide us feedback on your experiences through our newsgroup.

The EclipseLink Team

Tuesday, April 7, 2009

SDO 2.1.1 (JSR-235) Releases with EclipseLink as the Reference Implementation

I am happy to announce that SDO 2.1.1 (JSR-235) has been approved by the JCP, and EclipseLink SDO is the reference implementation.

EclipseLink Download

Reference Implementation Download

SDO is a generic structure to represent data from many sources such as XML and relational databases, most commonly associated with SCA.

EclipseLink SDO was implemented as a thin layer on top of EclipseLink's object-to-XML layer (which is also the base for EclipseLink JAXB). EclipseLink SDO can be used alone, or as a means to expose POJOs as DataObjects so that components like EclipseLink JPA and JAXB can be used.

Accessing Relational Data as SDO DataObjects using JPA

Converting POJOs to/from SDO DataObjects using the POJO/SDO Bridge

Thank you to all of the EclipseLink committers that contributed to the SDO component.

Wednesday, March 25, 2009

New EclipseLink Logo

We have wrapped up our EclipseLink logo contest and we have a winner.

Thanks to everyone who submitted a logo, commented on the submissions, or voted for their favorite. You can see the image in use on the home page.


Thursday, March 12, 2009

EclipseLink 1.1.0 Released!

I am happy to announce that EclipseLink 1.1.0 is now available for download.

There are some useful links off of the download page including a 'getting started page', and the 'release notes' for 1.1.0.

As well as bug fixes, 1.1.0 introduces feature enhancements in the following areas:

The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures).

EclipseLink 1.1.0 JPA support is extended to introduce:

  • a new 1:M mapping that doesn't require a back pointer or a separate join table to hold the associations.

  • TABLE_PER_CLASS Inheritance has been added giving greater flexibility in how your relational tables associate with the classes in a hierarchy.

This release of EclipseLink includes an implementation of SDO 2.1.1 (JSR 235). This implementation conforms to the final draft and is being included with the final draft as the reference implementation.

Peter Krogh and Doug Clarke

Tuesday, March 10, 2009

EclipseLink at EclipseCon

EclipseCon is fast approaching. It occurs between March 23 and March 26. There
are a number of sessions that would be of interest to EclipseLink users.

There is one tutorial:

Four talks:

Two BOFs:

We hope to see you there.

Wednesday, March 4, 2009

EclipseLink Logo Contest

We have just kicked off the EclipseLink Logo Contest to come up with an image we can use for the web, presentations, and other miscellaneous purposes. We are inviting all interested parties to both contribute ideas, provide feedback, and vote for their favorite.

We have had a variety of logos for TopLink over the years.

The first proposal is from one of our committers, Rick Sapir, connects us back to the original bridge between worlds logo. So far this is our only submission but definitely my favorite :)

All proposals will be posted to the contest page:

To submit a proposal, provide feedback, or vote please use the bug link provided on the contest page.