Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Presentations/Abstracts"
(→Building JPA Applications with Eclipse JPA and Dali) |
(→Eclipse MOXy: Freedom through XML Binding) |
||
| Line 23: | Line 23: | ||
== MOXy Talks == | == MOXy Talks == | ||
| − | === | + | === EclipseLink MOXy: Freedom through XML Binding === |
The use of XML throughout the Java community is extensive and growing. And developers are faced with a number of options when dealing with XML in their Java applications. The most important question is whether to work directly with the XML DOM or to use Object-XML Mapping (OXM, a.k.a. XML Binding). Mapping XML to a domain object model simplifies Java development by allowing developers to work with rich objects instead of generic DOM elements. OXM is gaining popularity in the Java community but not all OXM frameworks are equal. When selecting an OXM framework for a project it is important to consider performance, standards compliance, usability and flexibility. In this session attendees will be introduced to OXM and to how these issues are addressed by EclipseLink MOXy, a component of the the Eclipse Java Persistence Platform. EclipseLink provides a rich OXM solution that addresses a wide range of application requirements while also providing the benefit of integration with other EclipseLink persistence capabilities. | The use of XML throughout the Java community is extensive and growing. And developers are faced with a number of options when dealing with XML in their Java applications. The most important question is whether to work directly with the XML DOM or to use Object-XML Mapping (OXM, a.k.a. XML Binding). Mapping XML to a domain object model simplifies Java development by allowing developers to work with rich objects instead of generic DOM elements. OXM is gaining popularity in the Java community but not all OXM frameworks are equal. When selecting an OXM framework for a project it is important to consider performance, standards compliance, usability and flexibility. In this session attendees will be introduced to OXM and to how these issues are addressed by EclipseLink MOXy, a component of the the Eclipse Java Persistence Platform. EclipseLink provides a rich OXM solution that addresses a wide range of application requirements while also providing the benefit of integration with other EclipseLink persistence capabilities. | ||
Revision as of 10:45, 15 November 2007
This page is dedicated to collecting abstracts for talks and tutorials on EclipseLink. These abstracts are developed colaboratively by interested speakers and used to propose talks at upcoming conferences.
Contents
General Talks
Introducing EclipseLink--the Eclipse Persistence Services Project (Full Monty)
The creation of EclipseLink, the Eclipse Persistence Services Project, signals the inauguration of a new generation of Java persistence where all of the dominant persistence standards are implemented and accessible from a single source. EclipseLink is composed of a set of separate runtime components that can be used in both clients and servers, and is the first open source project to offer a full suite of persistence technologies. By supporting all of the popular standards, including object-relational mapping using the Java Persistence API (JPA), object-to-XML mapping through the Java API for XML Binding (JAXB), and loosely bound Service Data Objects (SDO) that bridge the relational and XML worlds, EclipseLink will provide the most comprehensive persistence platform available. Equally compelling is the fact that these technologies are offered with a rich array of feature extensions and high-end performance options.
In this session, attendees will learn what EclipseLink is, the standard technologies it implements, and how these technologies can be used separately or together to meet advanced and diverse application requirements. We will show examples of how to use EclipseLink to map Java objects in object-relational and object-XML contexts, and how it can be used in any runtime environment, including Eclipse RCP, Java SE, Java EE, Spring and Tomcat.
JPA Talks
Eclipse JPA: Getting Chocolate in the Peanut Butter
Eclipse has lived most of its life as an IDE, and most will agree that it has achieved a great deal of success along the way. However, Eclipse is now all grown up and has decided to establish itself in runtime-land as well. Counted in its runtime component arsenal is its Equinox OSGi layer, its Rich Client Platform (RCP) API, and now a full Java Persistence Platform that includes a deluxe Java Persistence API (JPA) implementation. In this talk we will learn how to use the Eclipse JPA runtime layer both inside and outside Eclipse. We will see how the Eclipse Dali tooling assists in developing a JPA application, and also see what configuration metadata might be needed to get the application running. As part of the discussion we will examine the difference between writing applications targeted for a full Java EE 5 container and those built to run in a standalone Java SE environment.
Attendees are not required to have experience with JPA, but having some kind of Java persistence knowledge or object-relational mapping experience will help.
Building JPA Applications with EclipseLink and Dali
With the release of Dali JPA Tools 1.0 and the availability of Eclipse JPA from the EclipseLink project, a complete JPA development platform and runtime environment are now available from Eclipse. In this talk we'll learn how to use the Eclipse JPA runtime but also see how the Dali tooling provides a platform for developing portable persistence applications across all compliant JPA providers. We'll look at JPA object-relational mappings and what configuration metadata is needed to get an application up and running. As part of the discussion we'll examine the difference between writing applications targeted for a full Java EE 5 container and those built to run in a standalone Java SE environment and how Dali's integration with the Web Tools Platform supports development for a variety of runtime environments.
MOXy Talks
EclipseLink MOXy: Freedom through XML Binding
The use of XML throughout the Java community is extensive and growing. And developers are faced with a number of options when dealing with XML in their Java applications. The most important question is whether to work directly with the XML DOM or to use Object-XML Mapping (OXM, a.k.a. XML Binding). Mapping XML to a domain object model simplifies Java development by allowing developers to work with rich objects instead of generic DOM elements. OXM is gaining popularity in the Java community but not all OXM frameworks are equal. When selecting an OXM framework for a project it is important to consider performance, standards compliance, usability and flexibility. In this session attendees will be introduced to OXM and to how these issues are addressed by EclipseLink MOXy, a component of the the Eclipse Java Persistence Platform. EclipseLink provides a rich OXM solution that addresses a wide range of application requirements while also providing the benefit of integration with other EclipseLink persistence capabilities.