+1 sure.
Else the end users will be lost :)
FYI, I raised KARAF-647 about this topic. Feel free to add your comments.
Regards
JB
On 05/18/2011 04:21 PM, mikevan wrote:
We should also provide some mechanism from the console to list all of the
available contexts.
Andreas Pieber wrote:
I think we should provide two methods here: one to store "command
context" (e.g. for camel context) and one for switching into
subcommand context. I'm not sure if we can handle this in the same
way.
I think it would be fine to be able to do:
root@karaf> camel:ctx xya
root@karaf #xya> camel:someCommand
root@karaf #xya> shell camel
root@karaf /camel/ #xya> someCommand
root@karaf /camel/ #xya> shell
root@karaf #xya>
...
I think you get my point. The shell part should be directly part of
karaf. For the ctx part we may be able to provide some general logic?
Kind regards,
Andreas
On Tue, May 17, 2011 at 10:24 PM, James Strachan
<[email protected]> wrote:
On 17 May 2011 20:54, mikevan<[email protected]> wrote:
Not really. I'm just thinking from an end-user perspective and how to
use
commands associated with a specfiic set of features. For example, if we
want to use camel-specific commands, what would the most intuitive way
be?
In previous posts, there were references to "context", which I (likely
misread) thought referred to a given set of shell-commands associated
with a
given feature. Ioannis referred to this is switching contexts, which
also
may be a bit misleading.
There's only one camel shell. However CamelContext is a quite
different camel thing; kinda like a Spring ApplicationContext or web
application context; there can be many of them inside any Karaf
container. Some commands in the camel shell refer to a specific
CamelContext instance which folks may wish to default to use across
different commands.
So the part of this thread talking about associating camel contexts to
the camel commands was analogous to associating web commands to a
particular web application - so its not really related to switching or
entering/leaving shells, its more to do with environment variables
that commands use (to use the unix shell analogy).
--
James
-------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com/
-----
Mike Van (aka karafman)
Karaf Team (Contributor)
--
View this message in context:
http://karaf.922171.n3.nabble.com/PROPOSAL-Shell-commands-context-support-tp2951532p2957140.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
