Eike Stepper

But what if:

• you require more enterprise-like model persistence than XML serialization?
• your application has to be available for multiple users at the same time?
• your model resources are too huge to fit them into XML files?
• you need object grained locking and transactions that span multiple resources?
• your users appreciate to always look at the latest state of the central model?
• they could simply switch back their view of the model to historical states?

The Connected Data Objects (CDO) model repository and distributed shared model for EMF delivers solutions to the afore mentioned challenges and more. CDO is a component of the EMFT subproject for many years now and the latest generation has a completely new design and a bunch of cool new features.

Talk Agenda

Introduction

• Brief introduction of the author and presenter
• The motivation behind and the history of CDO
• Overview of the CDO architecture

Demonstration

• Detailed and live demo of CDO in a typical deployment scenario
• Discussion of alternative deployment scenarios
• Live development of a CDO capable model

Insights

• Detailed discussion of the different layers of CDO
  • Server (the model repository and storage framework)
  • Protocol (a Net4j network protocol)
  • Client (the distributed shared model)
• Information about configuration and optimizations
  • Repository configuration files
  • Chunked collections
  • Intelligent prefetching
  • Model usage analyzers
• Different ways to integrate EMF models
  • Generating for CDO
  • Dynamic models
  • Legacy models
• Ways to extend CDO
  • Pluggable storage framework
  • Pluggable database adapters
  • Pluggable mapping strategies
  • Managed containers

Conclusion

• Summary of the important aspects that make CDO unique
• Survey of the CDO homepage
• Discussion about possible future directions
• Questions

CDO Homepage

Gold sponsors

Silver sponsors

Hardware sponsor

Media sponsors

Be a Sponsor