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.
SMILA/Documentation/2011.Simplification
We are currently working in a branch on simplifying some core concepts of SMILA.
The URL of the branch is:
https://dev.eclipse.org/svnroot/rt/org.eclipse.smila/branches/2011-02-24_Simplification
On this page we will link new versions of documentation pages that changed because of these simplifications. When the branch is merged back to the trunk, these pages will replace the normal documentation pages under SMILA/Documentation.
The topics are:
Remove support for Processing Services in BPEL pipelines
The idea behind the distinction between pipelets and processing services was to distinguish between small lightweight processing elements (pipelets) and big ones that require more control on the lifecycle and the used resources. However, we realized that the same goal can be achieved by calling a standard OSGi service via small pipelets. This way the service can have a meaningful interface (instead of having to support a single process() method), the developer has clearer guidance on how to implement the needed functionality and last but not least the implementation of th BPEL engine integration becomes easier.
- Workflow Processing
- Integration Guides
- ProcessingServices converted to Pipelets
- Semantic Layer: Ontology Integration
- Other Changes to be done
- TODO SMILA/Glossary (remove "Processing Service" definition, edit "Pipelet" definition)
- TODO SMILA/FAQ (Processing Service rauswerfen)
- TODO SMILA/Default configuration workflow overview
- TODO SMILA/Documentation ("Pipelets and ProcessingServices"-Link ändern in "Pipelets")
- SMILA/Development Guidelines/How to write a ProcessingService has been removed.
Replace Tomcat by Jetty 7 as the embedded HTTP server
Simplify Data Model
We also realized that the SMILA data model is too complex to understand and work with. Also it does not really match well to requirements like having to provide JSON based HTTP ReST services which we had in projects using SMILA.
- General
- Data Model
- Workflow Processing
- ProcessingServices converted to Pipelets
- Semantic Layer: Ontology Integration
- Connectivity
- Crawlers
- Agents
- Compounds
- Security
- Other Changes to be done
- Adapt configuration examples on
- Check "record" entry in glossary ("parameters" not mentioned?)
- Remove Java Interfaces from (and link to javadoc instead?)
- Adapt RecordFilter examples on SMILA/Documentation/QueueWorker
- Remove, because outdated or obsolete (or move some Attics page?)