I must have missed that. In this case we do not need to hurry with a new
schema. I will
prepare a schema and some demo code as soon as 3.0 is out.
At the moment I think the best starting point is this for the xml:
<shell:action
class="org.apache.karaf.admin.command.ChangeRmiServerPortCommand">
<property name="adminService" ref="adminService" />
<shell:completer ref="instanceCompleter" />
</shell:action>
For the annotation based config we could do something like:
|@Command(scope = "test", name = "hello", description="Says hello")
@Completer{beanId="myCompleter"}
@Service
public class HelloShellCommand implements Action {
@Inject(ref="|blueprintBundleContext|")
BundleContext context;
@Override
protected Object doExecute() throws Exception {
System.out.println("Executing Hello command");
return null;
}
}|
Btw. the annotation based config would allow to have a parent class with
a common service that gets injected. So not every command has to do it.
I think it might
make a lot off sense to use annotation based config in karaf itself as
it requires much less code. It also reacts nicer when doing refactorings
as it cant happen that you still
refer to the old class name.
Christian
Am 09.05.2012 19:50, schrieb Guillaume Nodet:
The 1.1.0 version has already been released from the 2.x branch, so it has
to be a 1.2 if we keep the old elements in the same schema, or a 2.0 if we
remove the old elements from the schema (even if the handler implementation
supports both namespaces).
On Wed, May 9, 2012 at 6:59 PM, Christian Schneider<[email protected]
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
