Archived Technology Projects

Projects under the Eclipse Technology Project have limited lifecycles. Unlike the major top-level Projects, the Technology Projects are meant to be technology explorations or incubators. When these projects have explored, proved, or disproved their associated technologies, the project comes to its natural end. For some projects, this end is a paper publishing the research results; for others, this end is to be incorporated into the base technology of another top-level project.

Archived newsgroups and mailing lists are also available separately.

ALF

The ALF website, newsgroup, mailing list, source code, etc. are available in a compressed tar archive (342Mb)

CME

The CME website, newsgroup, mailing list, source code, etc. are available in a compressed tar archive (256Mb)

Koi

Koi version 1.0 is functionally complete and currently used in commercial Eclipse add-ons. Koi provides a intra-workspace communication platform for development of collaborative Eclipse features. Examples of collaborative features that are possible using Koi range from the relatively simple such as event notification (check-in, check-out, conflicting changes, etc.) to something as complex a supporting remote pair programming. 

The Koi infrastructure is built around a client/server architecture using a Web Services RPC communications model. The clients are individual eclipse platform instances that communicate with a "collaboration server" that supports data persistence and implements shared collaborative services. The base infrastructure also includes some base services such as user identification/authentication, client-to-client messaging, and event notification.

The Koi website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive (6.5Mb).

Dali EJB Object-Relational Mapping Project

The goal of Dali is to build support for the definition and editing of Object-Relational Mappings (ORM) for EJB 3.0 Entities (JSR 220). EJB 3.0 is part of the Java EE 5 specification (JSR 244). Dali is comprised of a set of extensible frameworks and exemplary tools designed to reduce the complexity of ORM by providing creation and automated initial mapping wizards, code assistance, and dynamic problem identification.

This project has moved from the Technology PMC to the Web Tools Platform project.

The Dali website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive (6.5Mb).

IDE for Laszlo

IDE for Laszlo is an Eclipse-based development environment for creating, editing, debugging, and testing applications based on the LZX declarative mark-up language. Laszlo is based on LZX, which is an XML and JavaScript description language similar in spirit to XUL (XML User interface Language) and XAML ("Longhorn" mark-up language by Microsoft™).

The Laszlo Platform is an open-source platform for the development and delivery of Rich Internet applications (see http://www.openlaszlo.org for more information) where the LZX XML mark-up is used to create the user interfaces.

The Laszlo website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive. (9MB)

Lepido, Tools for Apache Cocoon

The Lepido website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive (9MB)

OMELET (Open Modeling Environment with Links for Extensions and Transformations)

The Open Modeling Environment with Links for Extension by Transformation project aimed to provide the ability to integrate the increasingly wide variety of modeling transformation technologies and tools so that otherwise incompatible tools could be used in combination. As such OMELET could be viewed as a next generation make, using meta-models to give strict type signatures for models and transformations between models.

Successes
OMELET demonstrated an ability to integrate various tools, supporting transformations written in Java, XSLT1, XSLT2, or ANT. OMELET pioneered a multi-level typing system for meta-models so that a model comforming to a meta-model could be described as a file representation of an XML 1.0 serialization of an XMI 1.3 encoding of a UML 1.4 meta-model, thereby allowing transformations to operate at appropriate levels of abstraction. Work in progress supported ATL, Tefkat, a simple composite transformation language and a set of Ecores for various MOF and UML standards.

Failures
OMELET never acquired sufficient resources to progress at a satisfactory rate. Lack of resources was a particular problem for an integration project since it was too easy to be distracted into looking at every other interesting modeling project and concluding that yes that too would be good to integrate with OMELET. Lack of resources also prevents the release of MOF and UML models since licensing issues were never resolved.

Final status
OMELET was just about functional with respect to invoking individual transformations, but that was more sensibly done within the environment of that transformation. OMELET was close to supporting composite transformations at which point OMELET would become useful.

Prior to archiving, the prevailing CVS status was upgraded to support Eclipse 3.1 and Java 5. The final release on the update site needed the Eclipse 3.1M4 release to avoid problems with early Eclipse support for Java 5. 

The MDDi project has almost identical goals to OMELET and significantly greater resources. It is therefore hoped that MDDi can fulfill OMELET's ambitions. 

The OMELET website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive (2mb)

Pollinate

Goals Achieved

Pollinate is an Eclipse technology project for build an Eclipse-based IDE and toolset that leverages open source application frameworks Apache Beehive and platforms like Web Tools Platform. There is a tight focus on Beehive related functionality making everything else that Pollinate needs secondary. >From inception until work ended at the end of Q1 2005, Pollinate focused on building on WTP to address Apache Beehive NetUI and PageFlows, leaving Controls and Web Services MetaData for the future. To that end, there is a basic Page Flow Editor in Pollinate plus basic support for assembling and launching a Beehive based web application.

Final Status

At this time the Pollinate Project is in archival. We would welcome others from the community who are interested in Pollinate to step-up and lead or contribute to the project.

The Pollinate website, newsgroup, mailing list, source code, and latest downloads are available in a compressed tar archive (155Mb)

More information

Visit beehive.apache.org for more information on the apache beehive project. Visit www.eclipse.org/webtools for information about the web tools project. Additional resources are available at dev2dev.bea.com/opensource and dev2dev.bea.com/eclipse for articles, blogs and other related material.

Stellation

Stellation is a software configuration management system designed to be an extensible platform for building systems based on the integration of advanced or experimental SCM techniques with the Eclipse development environment. The Stellation project will be using this system to integrate support for fine-grained software artifacts into the Eclipse environment, with particular focus on dynamic program organization, and inter-program coordination.

The Stellation website, newsgroup, mailing list, source code, and latest download are available in a compressed tar archive (110Mb).

WSVT (Web Service Validation Tools)

The mission of the project is to provide a set of web service validation tools that can be used during the development, deployment, testing and debugging of web service applications... This project has moved from the Technology PMC to the Web Tools Platform project. (For archival reasons, the last independent release of WSVT is still available.)

XSD

The XSD Infoset Model is a reference library for use with any code that examines, creates or modifies XML Schemas (standalone or as part of other artifacts, such as XForms or WSDL documents)... This project has moved from the Technology PMC to the Eclipse Modeling Framework project.