Hi,
I'm evaluating cloverETL, and i'm particular interested in using it
within an OSGi container( Equinox or Felix.... ).
In the release notes of CloverETL 3.0 i read the following:
"CloverETL Server modularity based on OSGi standards"
Maybe i'm missing something, but looking at clover etl jars, i've not found typical
OSGi headers in manifest file.....
I understand ( and i like ) the modularity provided by clover engine that loads
clover plugins dinamically... but it seems that the way clover load plugins
is not based on "OSGi standards", but it relies on plugin.xml.
Despite this, what i'm really interested in is to know if the clover team
has in it's roadmap a plan for full "OSGi compliance" where for full OSGi compliance i
mean:
1) Having all clover jars, with compliance OSGi headers..
2) Migration of the current plugin system to an osgi stanadard ones...., looking at
cloverETL architecture OSGi declarative service will fit perfectly as a standard pllugin systems.
I like very much cloverETL architecture as it's now, and i think that would be not
difficult to move to OSGi, because as it's now the code is well written and organized, so
in my opinion a move to an architecture based on OSGi services would be great
and not so difficult to achieve....
Any thoughts???
Thx in advance....
Andrea Zoppello
I'm evaluating cloverETL, and i'm particular interested in using it
within an OSGi container( Equinox or Felix.... ).
In the release notes of CloverETL 3.0 i read the following:
"CloverETL Server modularity based on OSGi standards"
Maybe i'm missing something, but looking at clover etl jars, i've not found typical
OSGi headers in manifest file.....
I understand ( and i like ) the modularity provided by clover engine that loads
clover plugins dinamically... but it seems that the way clover load plugins
is not based on "OSGi standards", but it relies on plugin.xml.
Despite this, what i'm really interested in is to know if the clover team
has in it's roadmap a plan for full "OSGi compliance" where for full OSGi compliance i
mean:
1) Having all clover jars, with compliance OSGi headers..
2) Migration of the current plugin system to an osgi stanadard ones...., looking at
cloverETL architecture OSGi declarative service will fit perfectly as a standard pllugin systems.
I like very much cloverETL architecture as it's now, and i think that would be not
difficult to move to OSGi, because as it's now the code is well written and organized, so
in my opinion a move to an architecture based on OSGi services would be great
and not so difficult to achieve....
Any thoughts???
Thx in advance....
Andrea Zoppello
-
Hi,
"modularity based on OSGi standards" is implemented by CloverETL Server.
So you can implement you own server API as OSGi bundle.
This feature is briefly described in this section of online manual:
http://server-demo-ec2.cloveretl.com/cl ... /osgi.html
Regarding the CloverETL engine modularity, there is our own modularity implemented which is not based on OSGi standards.
We are currently considering benefits of OSGi modularity of clover engine. However it's not our priority for now.
Regards,
Martin -
Hi Martin,
Thnak you for your response, now i've understand better what it means
when you refer to "modularity based on OSGi standards".
I know very well the approach of embedding an OSGi container within the
"servlet-bridge" approach.
Basically if i've understand, you're going to embedd the OSGi framework to
the clover server...
BTW i'm interested ( and i've started ) this post, to evaluate to use clover embedded
in OSGi framework where clover core engine, and clover plugins would be osgi bundles
exposing OSGi service...
Sorry to hear that a move to OSGi is not in your priority...
my thougths on this, is beacuse looking at the clover code, in my opinion a move to osgi would
not to be a great problem, because as i said above in my opinion the code is well designed.
Regards
Andrea
Please sign in to leave a comment.
Comments 2