Monday, September 20, 2010
Title: Java Persistence API (JPA) 2.0 with EclipseLink
Hilton San Francisco, Golden Gate 4/5
Title: Advanced Enterprise Persistence
Hotel Nikko, Nikko Ballroom II
S314491: Effective XML: Leveraging JAXB and SDO
Hilton San Francisco, Yosemite A
S313434: Java Persistence API Futures BOF
Hilton San Francisco, Yosemite A
Title: Scaling JPA Applications with Oracle TopLink Grid and Oracle Coherence
Hilton San Francisco, Imperial Ballroom B
We also will be staffing exhibition booths on Oracle TopLink focusing on EclipseLink at the Oracle Fusion Middleware DEMOgrounds as well as helping staff the Oracle/Eclipse booth at the Java One exhibition hall and some time at the Eclipse Foundation booth.
We hope to meet as many EclipseLink users as possible and exchange ideas.
Thursday, August 5, 2010
The purpose of this blog post is to help a user we were assisting on Twitter who wanted to use JAXB to marshal JPA entities into XML but only wanted a portion of the entities to be used. By default JAXB will traverse all available relationships including lazy ones that have not been loaded to build a complete XML document for the provided entities.
Here is a simple example reading a Customer with an Address (1:1) and PhoneNumber(s) (1:M) from a database and marshalling it into XML using EclipseLink JPA with EclipseLink MOXy.
Setup code for JPA and JAXB:
// JPAExample: Find & Marshall Customer
EntityManagerFactory emf =
EntityManager em = emf.createEntityManager();
JAXBContext jaxbContext = JAXBContext.newInstance(Customer.class);
Customer customer = em.find(Customer.class, 1);When executed this generates the following XML and causes the customer's address and phone numbers to be loaded from the database.
Now, if we wanted to generate a partial XML document including only the Customer's basic attributes and its address's attributes we could use a copy group to create a partial copy and marshal it:
Customer customer = em.find(Customer.class, (long) 1);Now the generated XML appears as:
CopyGroup cg = new CopyGroup();
JpaEntityManger nativeEM = em.unwrap(JpaEntityManager.class);
Customer custCopy = (Customer) nativeEM .copy(customer, cg);
marshaller.marshal(custCopy , System.out);
There are other combined uses of AttributeGroup that can be used to control what is fetched and loaded as well but this copy example should illustrate some of the options available and how EclipseLink JPA and MOXy components can be easily used together.
Additional MOXy examples available here.
Wednesday, June 23, 2010
It is with great pleasure that I would like to announce the release of EclipseLink 2.1.0 (Helios). This release of brings a number of exciting features many of which were voted on, and chosen by the community.
Some of the JPA features included in this release are
- improved JPQL enhancements, and extensions including 'TREAT...AS' and 'FUNC'.
- Fetch, Load, Copy & Merge of partial entities using 'AttributeGroup'
- extentions to 'eclipselink-orm.xml'
- Dynamic Persistence: JPA without requiring Java classes.
- New Platforms: SAPNetWeaver Server Platform and Symfoware Database Platform
Some of the MOXy features included in this release are
- JAXB 2.2.0 certified
- JAXB without annotations using externalized mappings in XML
- 'Dynamic Persistence': XML Binding without Java classes.
Some of the SDO features included in this release are
- Support for EclipseLink SDO usage with 'WebSphere' and 'JBoss'
... and more...
Some of the DBWS features included in this release are
- Support DBWSBuilder-generated JAX-WS Provider on JRockit
- Support for Eclipse WTP Dynamic Web Project structure
For a full list of features, and download instructions please see http://wiki.eclipse.org/EclipseLink/Release/2.1.0 .We would like to thank everyone involved in the development of this release.
Peter Krogh and Douglas Clarke
Monday, May 31, 2010
Last week we held our first EclipseLink Summit here in Ottawa with attendees from Canada, Germany, India, and the US. The principal goal of the summit was the exchange of technical information and ideas. We believe the event was a tremendous success!
We spent 2 days with committers leading technical sessions discussing areas from high level components and architecture to the detailed workings of EclipseLink's querying, caching, transactions, management, diagnostics, metadata processing, JPA 2.0 metamodel, and several other subsystems.
We would like to extend a big thank you to all of the committers who lead those sessions. The preparation time invested was obvious and the quality was amazing. We know it was tough to squeeze this additional work into your hectic pre-Helios schedules. The feedback from all attendees was excellent.
On the 3rd day of the Summit we focused more on the project itself. Starting with a talk from Jeff McAffer (EclipseSource) on OSGi and Eclipse RT technologies. We then discussed EclipseLink and OSGi, documentation, development process, build, testing and our road map planning.
While not all of these sessions allowed us to come to concrete conclusions the discussions were great and will hopefully carry on in our weekly committer meetings where we continue to improve our processes and refine our direction.
For those interested a more detailed summary of our Thursday sessions will be published to the firstname.lastname@example.org mailing list and topics requiring further discussion will be added to the weekly meeting agenda.
Thanks again to all the presenters and attendees. We are all looking forward to future EclipseLInk Summits where we can gather committers, contributors, and and users to share ideas and grow our community.
Your Summit Program Committee
Doug Clarke, Peter Krogh, and Shaun Smith
Friday, April 9, 2010
All interested parties are welcome to participate.
More info on Summit is available here.