Community
Participate
Working Groups
The e2e example uses JMX and reporting. We would like to have a more simplistic example that does not require anything else other than the DC framework. The input (datasource) can be an simple random or sequential number generator. The output (sink) can be directed to the console. There are some existing exmaples that can be mined to serve as a basis. The code can be in org.eclipse.cosmos.examples.dc.simple
Created attachment 75347 [details] Ant startup scipt to execute DC standalone This script constructs an OSGi environment for executing the COSMOS DC and starts the runtime. The script depends on the following paths being set: <target name="init"> <basename property="NAME" file="${basedir}"/> <property name="COSMOS_HOME" value="./COSMOS/plugins"/> <property name="CONFIG_TEMPLATE_HOME" value="./"/> <property name="ECLIPSE_HOME" value="C:\sbin\eclipse\europa\eclipse\plugins"/> <property name="PLUGINS_DIR" value="${basedir}/plugins"/> </target> The COSMOS_HOME variable contains the set of COSMOS bundles exported from your Eclipse environment (using Export->Plug-in Development->Deployable plug-ins and features option). The ECLIPSE_HOME variable should point to your Eclipse install location. The script expects that your Eclipse install is properly configured to build and run COSMOS (i.e. that you are currently using this Eclipse install to develop COSMOS). The CONFIG_TEMPLATE_HOME is the location of the config.ini template that the script will use to create an appropriate config.ini to launch your environment. This template is provided in a subsequent attachement.
Created attachment 75348 [details] config.ini template used by startup script This attachement contains the config.ini template that the previous build.xml attachement requires in order to create an OSGi environment for executing the COSMOS DC runtime.
This simple example was to be based on the CBE example. That example is not working. It is still a work in progress.
This has been open for a long time... Life has changed some over the past six months... Closing this and marking as a dup of 212189; we should ensure that this ER gets done in i8. *** This bug has been marked as a duplicate of bug 212189 ***
Correcting erroneous "future" milestone.
