Christian Ernst, Markus Kuppe

Christian Ernst, Markus Kuppe Markus Kuppe

Biography:

Markus Kuppe is a software engineer at Versant Germany focusing on Eclipse/OSGi and JDO/JVI related development. Besides being a frequent contributor to various aspects of Eclipse, he's a committer on the SoC and ECF projects and used to be a committer on Dali JPA. He is an open source enthusiast at heart since he first came into contact with Eclipse in 2001. He holds a B.Sc. in Computer Science from the Hamburg University of Applied Sciences.

Christian Ernst has been a software engineer with Versant Germany since 2005. He has a strong background in JDO and other persistence technologies. As a student he first gained experience with JDO and developed a Query Engine for JDOQL for the Fastobjects product (Poet) as his Diploma Thesis. Since than he has worked as a Java Consultant using JDO and as an Engineer for Würth-Phoenix Italy where he was responsible for porting the Zeus Application Server to JDO using KODO and Oracle RDBMS. He is also Versant’s offical member of  the JDO 2.0 expert group (JSR 243).
Christian holds a diploma in Software Engineering from the Hamburg University of Applied Sciences.

"An Eclipse Toolchain for Rapid Java Development Using Transparent Persistence"

Throughout the last decade Java has grown to become one of the most important programming languages for enterprise application development.
With Versant's enterprise OODBMS it has been possible to use different transparent persistence technologies like JPA, JVI or JDO for many years.
The Eclipse platform and the associated project portfolio has emerged as the de-facto standard for enterprise Java development. In this talk we will show how this toolchain can be supplemented to form a consistent and integrated development environment for building OODBMS powered enterprise applications.
This talk will conclude in a QA session that also serves as a way to solicit feedback from community members as the kinds of tools they would like to see or need for their day-to-day OODBMS development.