Absolutely the idea of publishing an action as a service should also
make defining command with SCR APIs much simpler. If you look at the SCR
commands in karaf they are complex. If you just had to publish the
Action as a service they would look much nicer. Currently there is one
action and one command per scr command. This would simply turn into the
action + scr annotations for publishing.
Personally I dont like the scr syntax too much but users would have the
option to use it.
Christian
Am 10.05.2012 23:59, schrieb sully6768:
Christian,
I know there are lots of options out there but is there a reason why you
wouldn't consider the SCR APIs that are now included with Karaf? I
implemented the module commands and management components using the SCR API
in combination with the BND Annotation for reference. The annotations,
which are build-time only, are used to generate the SCR XML document so
there isn't any need for getting into the gory details of the wiring.
Just a thought.
Best Regards,
Scott ES
http://fusesource.com
--
View this message in context:
http://karaf.922171.n3.nabble.com/Simpler-karaf-shell-command-action-definition-tp3974398p3978396.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
