Agree with Gert,
shell module of the features project is the most logical.
Regards
JB
On 01/19/2012 02:18 PM, Gert Vanthienen wrote:
L.S.,
Personally, I would add them to the features project, something
features/shell/jdbc and features/shell/jms probably. That will make it
easy for them to get released together with the rest of the project. We're
planning to both a 4.4.1 and 4.5.0 release in the next few weeks or months,
so those bundles could be part of both of those releases. Once the shell
bundles have been released, they can always be used outside of ServiceMix
in a plain Karaf as well if people would want to do that, so I would just
keep them in the main project source tree for now.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Thu, Jan 19, 2012 at 1:46 PM, Christian Schneider<
[email protected]> wrote:
Hi Gert and JB,
thanks for your responses. Can you give me some hints where to put the
code. I can then provide a jira issue and a patch.
Christian
Am 19.01.2012 12:41, schrieb Jean-Baptiste Onofré:
Hi Christian,
for me, it makes sense to have it in ServiceMix.
It should be a kind of "isolated" module which can be loaded in Karaf
**without** ServiceMix.
I have a set of others commands in mind that could be interesting.
I already have more or less these commands in Kalumet.
Anyway, +1 for that Christian, and thanks.
Regards
JB
On 01/19/2012 11:24 AM, Christian Schneider wrote:
Hi,
as part of my Apache Karaf Tutorial about database access I have written
some handy Karaf shell commands for databases.
They are described with screen dumps in my Tutorial
http://www.liquid-reality.de/**x/LYBk<http://www.liquid-reality.de/x/LYBk>.
The code is on github:
https://github.com/cschneider/**Karaf-Tutorial/tree/master/db/**command<https://github.com/cschneider/Karaf-Tutorial/tree/master/db/command>
Especially for embedded databases like derby and h2 I missed a simple
access to the database for a long time. So I think these commands could
be interesting for many developers.
Those commands might fit nicely into the scope of servicemix as they
support integration developers.
I am also planning to add a command set for jms that works in a similar
way:
jms:select -> select ConnectionFactory to use
jms:create-dest -> create destination
jms:delete-dest -> delete destination
jms:list -> list destinations
jms:browse -> browse queue
jms:send -> send message
jms:move -> move a message from one dest to another
jms:listen -> Watch live messages
So what do you think?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
