Architected Futures™

Tools and strategies ... for boiling the ocean

EATS

EATS Extension - Resource

Description

Resources are specialized versions of components which extend the C_AF_ResourceProvider implementation of the C_AF_FifoDispatcher.

EATS Extension Points

Introduction

The purpose of this section is to describe EATS Extension Points.

Core Extension Points

Component

Service

Resource

 

Reference

  • [Freelinking: Invalid Node ID “358”]

EATS Infrastructure Prototype Code Published

Submitted by joe.vansteen on Tue, 10/16/2012 - 16:44

My previous blog post, titled EATS Development Journal, provided a forward view of EATS development based on the Eclipse framework. This post announces the publication of the baseline code for that development effort. It provides the first in a series of posts which examine the code as a model for the infrastructure layer of the tool suite architecture.

EATS Target Platform Definition

Purpose

By default the Eclipse development workbench will target a version of itself as the execution environment for developed systems. Some of the problems with this include:

  • projecting execution to occur on the same platform as development (e.g., Windows, Mac, Linux)
  • unnecessary Inclusion of developer tools in the execution environment
  • difficulty in managing plug-in and related updates to the developed product

The Eclipse solution to this problem is the creation of a target platform specification for the developed product.

Eclipse Configuration

Overview​

For what we want to achieve, we are sometimes forced to work with back-leveled environments. To enable management of this we have adopted a dual (or multi-) path tracking of our development environment.

Eclipse Kepler Environment

Overview​

This is the configuration documentation for the EATS Eclipse development environment based on Eclipse project Kepler release levels. It was initially created as a Juno release level environment when we targeted EATS to be an Eclipse 4 application. It corresponds to EATS v4.2. It was migrated from Juno to Kepler via an update-in-place.

Eclipse Release Synchronization

The initial objective is to test uDig for use as both a workbench application for geospatial mapping and for use as a geospatial sub-component of an EATS workstation. The desire for EATS is to be able to configure a reasonably "up-to-date" Eclipse workbench application. Currently this would be a Kepler version workstation. The desire is to be able to evolve this workstation, over time, on a regular basis with new, current Eclipse project components.

Pages

Subscribe to EATS
SystemsThinking