Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse as a Runtime Catalog"
m (→Template: fix template) |
|||
| Line 12: | Line 12: | ||
=====<project and/or component name>===== | =====<project and/or component name>===== | ||
|- | |- | ||
| − | + | |'''URL:''' || <link to project/component page (web or wiki)> | |
|- | |- | ||
|'''Contact:''' || <person name/email address or mailing list> | |'''Contact:''' || <person name/email address or mailing list> | ||
Revision as of 01:21, 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.
Contents
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 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. |
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. |