I've just yet tried out the tool, haven't tested extensively as noted.
But I must confess beforehand that I can't be impartial because I
usually prefer simple command line tools over GUIs whenever possible
so basically I love the idea of a CLI management tool. I believe GUIs
are useful mostly when you don't know exactly what you're doing, CLI
tools are more effective otherwise. They also have this huge advantage
of unlimited possibilities for automation.
We have some specialized GUI tools tailored specifically for our use
cases (like profile editing of tables based on a commonly used profile
specification) which are more visually appealing and simpler compared
to JBoss's jmx-console. However, I guess I'll prefer Twiddle for
multiple reasons:
- it is a standard tool (or so I hope :) ), which means it should be
available in all deployments;
- it might be the only choice in some limited environments (no X
server, strict networking settings, where I would be setting up
multiple SSH tunnels just to fire up a "nice" GUI tool to change a
value of a MBean property).
As a Mobicents user and a developer of solutions based on the platform
I'm really grateful that this tool has been introduced. :) I believe
it'll become a crucial tool especially in some critical
troubleshooting situations. Will report if I stumble on any issues
later on or come up with any more suggestions.
Thanks,
Vilius
On Oct 20, 6:10 pm, Bartosz Baranowski <
baran...@gmail.com> wrote:
> yes, that was on my mind. Someone said: "what for" :) Thats his answer.
> Would like to hear more about overall impression and "look & feel" since
> this is first rel.
> Bartosz Baranowski
> JBoss R & D
> ==================================
> Word of criticism meant to improve is always step forward.
>