Skip to main content
Jump to: navigation, search

Difference between revisions of "Eclipse as a Runtime Catalog"

(Runtimes)
Line 121: Line 121:
  
 
----
 
----
 +
 +
{| width="100%"
 +
|- style="background:#cacae4"
 +
!colspan="2" |
 +
=====Swordfish=====
 +
|-
 +
|'''URL:''' || [http://eclipse.org/swordfish Swordfish web site]
 +
|-
 +
|'''Contact:''' || Oliver Wolf, oliver.wolf@sopera.de, swordfish-dev@eclipse.org
 +
|-valign="top"
 +
|'''Description:''' || The goal of the [[Swordfish]] project is to provide an extensible service-oriented architecture (SOA) framework that can be complemented by additional open source or commercial components such as a service registry, a messaging system, a BPEL engine etc. to form a comprehensive open source SOA runtime environment based on both established and emerging open standards.
 +
|}

Revision as of 05:37, 31 October 2007

Eclipse began as a tooling platform. In the 3.0 timeframe it emerged as a Rich Client Platform (RCP). Eclipse continues to evolve and is now being used more and more as a runtime technology. This is not entirely new; various projects such as Equinox, eRCP and ECF have been around a while and are entirely runtime focused. More recently however there has been a flurry of activity in the space: RAP shipped 1.0, the Swordfish, Riena and EclipseLink projects have been proposed, ... And that's not to mention the commercial adoption of various Eclipse runtime technologies.

Despite this success, the Eclipse community can do more. One idea is to create a catalog of runtime-related technologies in Eclipse projects today. For example, projects such as EMF and BIRT have non-trivial runtime components but this goes largely unnoticed or underrated by many. This wiki page is an effort to informally gather a list of such technologies so the community can get a bigger view of the overall picture.

Template

If you are working on a project that is hosted at Eclipse.org that is runtime related, please add some details below roughly using the following template.

<project and/or component name>
URL: <link to project/component page (web or wiki)>
Contact: <person name/email address or mailing list>
Description: <no more than a paragraph or so summarizing the technology. Please include lots of links to more info>

Runtimes

BIRT
URL: BIRT web site
Contact: Wenfeng Li, birt-dev@eclipse.org
Description: BIRT is a BI and Reporting Tools platform. In addition to a graphical report designer, it has a OSGi based runtime component to allow developers to deploy BIRT reports as well as BIRT extensions: such as data access ODA drivers, business logic calculation components, security/encryption extensions, output format emitters, charting library, and report library to application servers.

Eclipse Communication Framework (ECF)
URL: ECF web site
Contact: Scott Lewis, ecf-dev@eclipse.org
Description: ECF is a framework for building messaging and communications into Eclipse-based tools. ECF APIs allow runtimes to communicate as well as allow people to communicate. For example, the discovery API, remote services API, and datashare API enable remote service discovery and access. These as well as other components of ECF provide runtime support for the creation of distributed applications.

Eclipse Modeling Framework (EMF)
URL: EMF web site
Contact: Ed Merks, emf-dev@eclipse.org
Description: EMF is a modeling framework and code generation facility for building tools and other applications based on a structured data model. From a model specification described in XMI, EMF provides tools and runtime support to produce a set of Java classes for the model, along with a set of adapter classes that enable viewing and command-based editing of the model, and a basic editor. EMF also includes Model Query, Model Transaction, and a Validation Framework. More...

Eclipse Persistence Services Project (EclipseLink)
URL: EclipseLink web site
Contact: Doug Clarke or Peter Krogh, ecliselink-dev@eclipse.org
Description: EclipseLink is a comprehensive persistence solution for Java developers. Delivering support around leading standards (JPA, JAXB, and SDO) as well as going beyond these to deliver high performance, scalability, flexibility, and developer productivity. EclipseLink was initiated from the contribution of the complete functionality of Oracle's TopLink product providing a enterprise-class solution with over 12 years of industry usage.

Equinox
URL: Equinox web site
Contact: Jeff McAffer, equinox-dev@eclipse.org
Description: Equinox is the base runtime for Eclipse. It includes an implementation of the OSGi framework as well as many standard and additional services. It is also home to p2, the new provisioning technology, the Eclipse server-side infrastructure and work in security support, componentized aspect-oriented support and other runtime infrastructure.

CDO (Connected Data Objects)
URL: CDO Wiki
Contact: Eike Stepper, stepper@esc-net.de, EMFT Newsgroup
Description: CDO is a 3-tiers solution for distributed shared models and a complete model repository server. With CDO you can easily enhance your existing EMF models in such a way that they can be stored and subsequently maintained in a central model repository. While object relational mapping against a JDBC data source on the server side is the shipped default CDO provides for pluggable storage adapters that allow you to develop and use different mappers (like Hibernate- or OODB-based). On the client side CDO provides a default integration with EMF, the Eclipse Modeling Framework, although other model integrations on top of the CDO protocol are imaginable as well.

Net4j
URL: Net4j Wiki
Contact: Eike Stepper, stepper@esc-net.de, EMFT Newsgroup
Description: Net4j is an extensible client-server communications platform based on OSGi but also executable stand alone. You can easily extend the protocol stack with Eclipse plugins that provide new transport or application protocols. Net4j's focus on performance and scalability is featured by non-blocking I/O, zero-copy signals and multiplexed binary protocols. Net4j was originally developed to support the CDO technology for distributed shared and persistent EMF models but can also multiplex your own user-supplied application protocols through the same socket connection.

Swordfish
URL: Swordfish web site
Contact: Oliver Wolf, oliver.wolf@sopera.de, swordfish-dev@eclipse.org
Description: The goal of the Swordfish project is to provide an extensible service-oriented architecture (SOA) framework that can be complemented by additional open source or commercial components such as a service registry, a messaging system, a BPEL engine etc. to form a comprehensive open source SOA runtime environment based on both established and emerging open standards.

Back to the top