Introduction to EclipseRT (JAX 2010)
by Chris Aniszczyk on May 06, 2010
- 1,824 views
A presentation about EclipseRT given at JAX 2010 in Mainz, Germany.
A presentation about EclipseRT given at JAX 2010 in Mainz, Germany.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 1
- Downloads
- 62
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,820
- Total Views
- 1,824
gklinkmann
* We are a trusted source of development tools and have significant mindshare in the Java space
* We started out as a tools framework but about 4-5 years ago we evolved into a platform for building rich client applications via an effort called RCP. Also around the time we launched the RCP effort we changed our plumbing to use something called OSGi which gave us a common and standard component model
* However, since that we have been growing in terms of projects and what people do at Eclipse... we have 200+ projects at Eclipse now and a variety of them have runtime aspects to them... we now have runtime containers via Jetty and Equinox
* We have enterprise frameworks
* Runtime containers such as Jetty and Equinox
* Persistence services with EclipseLink
* Data reporting support from BIRT
* Data modeling with Eclipse Modeling Framework (EMF)
* Remote communication and distributed OSGi with ECF
There was a conscious decision made 5 years ago to move to OSGi over our old plug-in model that we used when developing Eclipse plug-ins. It makes sense to go with a standard.
For example, NASA, the US space agency, uses EclipseRT for its Ensemble platform. Ensemble is used by the different science teams to write the applications needed to control and run the experiments on their Mars rover operations. Instead of each team writing their software from the ground up, they build on-top of the EclipseRT-based Ensemble platform. This results in an an acceleration of their software development efforts, a consistent end-user view of these applications and an interchange point between applications.
The component-oriented nature of EclipseRT and the OSGi standard creates a technology base that can be designed to be a platform. Architects can use the design and policy enforcement aspects available in EclipseRT to architect proper extension points and application development in their organization. Because the platform is built on-top of Eclipse technologies, developers can use their familiar tools and frameworks when developing for the platform instead of being forced to use custom platform tools. The deployment services available in p2 gives IT the ability to deploy and then maintain applications built on the platform.
Like Mark Little said in his presentation... we aren’t doing a good job of writing reliable code... the power of hardware is improving...
The traditional JEE stack tried to simplify things by providing a lot of “services” out of the box but this resulted in a monolithic stack and not much portability when moving across different middleware stacks... web profile is a step in the right direction but we prefer an approach that things come a la carte
Tthousands of developers working on a system and not really understanding what each other are doing… doesn’t sound like a safe thing to do. How are we going to make it possible for those people to collaborate effectively without stepping on each other?
Using the same principles employed in skyscrapers… foundations, frameworks and architectures.
I think EclipseRT is providing the solid foundations, frameworks and architectures that people need to build applications.
Of course Equinox is used as the base runtime across the Toast client, server and embedded elements. The example also demonstrates a wide range of OSGi services such as HttpService, ConfigAdmin, Log, ...
Server-side
Toast demonstrates three scenarios for the use of Equinox and OSGi on the server
p2 provisioning
Various elements of p2 are included in Toast; building, deploying, managing profiles, ...
ECF
Toast is a distributed application and uses ECF to do vehicle discovery, remote services and various other nifty things (Twitter?)
RAP
The Toast control center runs on servers and presents a rich user interface using RAP including Google Map and Earth integration.
EclipseLink
The control center needs to store and manage data about vehicles, drivers, packages, ..
Modeling
The basic Toast server side data is, of course, modeled using EMF.
BIRT
Toast allows for reporting on the activities of the vehicles, package delivery, ... through RAP integrated reportlets.
Riena
Riena is used to give users a rich client application experience using remote messaging and focused workflows.
Modularity
If all you need is a servlet engine and web server, why bring along EJB runtimes, a JMX framework,
If you're a developer, you shouldn't need to load 500 Java classes just to print "Hello World" to the console. Likewise, if you're running a Web CMS, you shouldn't need to wire together millions of dollars' worth of systems to light up a web browser.
EclipseRT is all about providing an ala-carte model when it comes to building your own runtime
Equinox provides one methodology that normalizes the decomposition of code into components and the collaboration between these components within, and across, tiers. The result is a system that has the feel of a tier-less architecture.
For example, NASA, the US space agency, uses EclipseRT for its Ensemble platform. Ensemble is used by the different science teams to write the applications needed to control and run the experiments on their Mars rover operations. Instead of each team writing their software from the ground up, they build on-top of the EclipseRT-based Ensemble platform. This results in an an acceleration of their software development efforts, a consistent end-user view of these applications and an interchange point between applications.