Hi Claus,
karaf uses namings like:
bundle:list
service:list
These are resource oriented what means that the scheme bundle references
a resource type.
camel:route-list
is not resource oriented. camel references a framwork.
camel-route:list
would be more similar to karaf. Of course we can not simply write
route:list as this would clash to soon with other frameworks.
Christian
Am 08.12.2011 12:54, schrieb Claus Ibsen:
Hi
On Thu, Dec 8, 2011 at 9:49 AM, Christian Schneider
<ch...@die-schneider.net> wrote:
I really like the idea of having camel:route and then simply call list or
start or stop.
We can even do that without the sub shells already by naming the commands
slightly different.
Instead
camel:route-list
camel:context-list
I propose to have:
camel-route:list
camel-context:list
This would be more similar to the later sub shell commands.
Interesting perspective.
However I like that everything related to camel is camel:xxxx-yyyy
Then you would know that camel: is the standard Camel shell plugin we provide.
Isn't the Karaf using that notation as well, so its bundle:xxx-yyy,
system:xxx-yyy etc
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
