Vendredi 20 janvier 2012 @ Sophia-Antipolis : soirée EclipseLink

Modifié par superadmin le 2022/07/19 16:09

Vendredi 20 janvier 2012 @ Sophia-Antipolis : soirée EclipseLink

Le Riviera JUG organise une rencontre *gratuite* sur le thème de EclipseLink le vendredi 20 janvier 2012 dans les locaux de l’INRIA Sophia-Antipolis.

Dès qu´on parle d´ORM ou de persistence, on pense brièvement à JPA puis on parle d´Hibernate, mais on oublie souvent que l´implémentation de référence de JPA c´est EclipseLink. Eh bien ce soir nous allons rectifier le tir, et vous présenter non seulement EclipseLink, mais encore mieux nous allons voir des aspects très pratiques de son utilisation.

En premier nous allons ainsi voir comment utiliser EclipseLink pour réaliser des applications Web RESTful, puis nous allons découvrir comment résoudre les problèmes de multitenancy. Le tout grâce à Shaun Smith, de Oracle, qui travaille sur EclipseLink et qui viendra nous faire le plaisir de nous présenter tout ça.

Réservation

Programme

Ce programme est susceptible de changer selon des imprévus prévisibles.

HoraireDescription
18:00 - 18:30Accueil — café
18:30 - 19:30EclipseLink: The Evolution of Java Persistence, par Shaun Smith
19:30 - 20:00Pause — buffet
20:00 - 21:00Multitenancy with EclipseLink, par Shaun Smith
21:00 - 21:30Fin/Rencontres — buffet

Sponsors

SponsorRôles
avisto-150.png  Sponsor annuel
lunatech-research-logo-small.png  Sponsor technique
inria-small-transp.gif   Salle

Pour venir

Salle « Euler Violet », bâtiment Euler en face du poste de garde (le gardien vous l’indiquera quand vous arriverez sur le site).

INRIA Sophia-Antipolis
2004, route des Lucioles
06902 Sophia Antipolis

Plan d’accès.

Prevoyez une pièce d’identité pour le poste de garde.


View Larger Map

Programme détaillé

EclipseLink: The Evolution of Java Persistence

Data access today isn’t just about reading and writing from relational databases anymore. It’s also about mapping your objects to XML and to JSON for use in RESTful web services. It’s about being able to persist your objects in NoSQL databases and being able to cache them in data grids so you can scale out your application to hundreds of servers. The EclipseLink project is well known as an object-relational mapping framework and as the JPA 2.0 reference implementation in Java EE 6, but it is evolving to provide a comprehensive set of data services for Java developers building enterprise and cloud applications in Java EE, Java SE, and in OSGi. In this session we’ll dive into these new services and see how to build modern enterprise Java applications leveraging EclipseLink both in the back end for data persistence and on the front end to build RESTful services that support HTML5 clients. Features will include:

  • EclipseLink “JSON-B”—provides Java/JSON binding similar to EclipseLink JAXB’s Java/XML binding. With JSON-B, developers can easily marshall their Java domain model to and from JSON which is the preferred format for HTML5/JavaScript clients.
    EclipseLink JPA-RS—provides a service that exposes JPA mapped entities over REST either as XML with JAXB or JSON with EclipseLink JSON-B. It supports a full CRUD API as well as named query invocation.
  • Resource Mapping—While JAXB and JSON-B provide a way to marshall to and from XML/JSON, RESTful services require a way to define what constitutes a resource. A naive approach of entity==resource may be used but is likely inefficient. With EclipseLink Resource Mapping the classes in a domain model can be declaratively mapped to a resource model which can be exposed using JPA-RS.
  • EclipseLink Dynamic Provisioning—provides persistence services to pure HTML5 applications without the need for Java classes. With Dynamic Provisioning, HTML5 clients can dynamically define storage requirements for a set of classes (object types) and EclipseLink will instantiate a full JPA-RS CRUD service for those classes as well as JPQL query support.

In addition to expanding the boundaries of Java persistence, EclipseLink is the JPA 2.1 reference implementation in Java EE 7. One of major themes of EE 7 is cloud deployment and multitenancy and EclipseLink has been blazing the trail by shipping support for both multitenancy and tenant specific extensions in the Eclipse Indigo release. EclipseLink multitenancy enables the use of a single persistence unit by multiple tenants while keeping their data isolated and secure. But to provide a SaaS platform EclipseLink also provides tenant specific extensions so that each tenant can augment JPA entities with the additional data they need to capture and maintain. In this section we'll:

  • Look at the challenges presented by multi-tenancy in Java EE and JPA
  • Explore the EclipseLink JPA multi-tenancy and extensibility features
  • Introduce the EclipseLink MOXy extensibility features that enable exposing multi-tenant and extended data over REST
  • Explore a complete multi-tenant Java EE application that supports dynamic tenant provisioning and customization

À propos des intervenants

Shaun Smith

shaun-smith.jpg

Shaun Smith is a Product Manager for Oracle TopLink and an active member of the Eclipse community. He's Ecosystem Development Lead for the EclipseLink project and a committer on the Eclipse Gemini Enterprise Modules, and the Dali Java Persistence Tools projects. Prior to joining Oracle Shaun was a consultant specializing in enterprise application architecture and agile software development. He's been involved with object persistence since 1996 starting with TopLink for Smalltalk and it's successor TopLink for Java. He's currently working on leveraging EclipseLink JPA and MOXy (JAXB and JSON binding) to accelerate the development of data services for HTML5 applications as well as Oracle TopLink Grid which supports the scaling out of EclipseLink JPA applications using Oracle Coherence.

Tags :
    

Prochains évènements

Anciens évènements

Donateurs

Faites un don au Riviera JUG pour financer les prochaines soirées :

Anciens et futurs donateurs

Sponsors du prochain JUG

This wiki is licensed under a Creative Commons 2.0 license
riviera
XWiki 14.10.13
contact@xwiki.com