On 25 January 2013 11:51, Łukasz Dywicki <l...@code-house.org> wrote:
Gentelmans,
Especially from Fuse. We have something similar already in Karaf repository and
it's called WebConsole. It been there since 2011. I'm sure you was aware of
that, especially Guilliaume.
I'm aware of most of the consoles at Apache yes.
There was example how to use it together with Camel and ServiceMix. But you
never took time to take a look on that.
How do you know? I did as it happens.
You decided to create another project instead of supporting existing Apache
community project. Or, I should be happy that you did not fork it?
I created another project. You got me there! I apologise for having
the cheek to create a project - I hope you will find it in your heart
to forgive me one day.
The main reason I did is the idea behind hawtio is to be make a
technology agnostic plugin based console. So its not OSGi specific or
Karaf specific; or Tomcat or Fuse Fabric or Camel or ActiveMQ
specific. Its a generic way to plug consoles together in a technology
agnostic way.
Thats why I didn't put it inside Apache Camel or Apache Karaf which
are specific frameworks and containers.
Though there's nothing stopping any project anywhere; inside Apache or
outside - of making a plugin for hawtio; or reusing hawtio inside its
own console, or exposing an existing console to hawtio.
We had the same problems with different web consoles, we saw that two years ago
when you started working on Fabric. Now you came here and rescue us.
Remember this is the camel list. Karaf web console doesn't really help
Camel folks terribly much. I created the original camel-web console;
the reason I'm back here is to say I've figured out a better way to do
the Camel console; thats way better & way smaller.
If I remember correctly that's third console you produced for Fabric (I don't
count previous Fuse consoles).
There is 1 console for Fuse Fabric; called FMC - which we're migrating
to be a plugin for hawtio; so that Fabric has 1 modular console which
anyone can extend. With anything. Like, oh I don't know, the Karaf web
console if anyone fancies. I hear its quite good.
I hope it will be latest and you will not drop the idea and continue supporting
it.
Gee thanks for your vote of confidence. We'll definitely be supporting
it & using it heavily.
Hawt.io structure (because is has no architecture) is same as Felix WebConsole.
if you're interested, the architecture is described here
http://hawt.io/developers/index.html
http://hawt.io/developers/plugins.html
In comparision Felix console uses OSGi services, your uses JMX.
A hawtio plugin can use REST / OSGi / JMX / whatever. But yeah, we're
using JMX by default for discovery as its the lowest common
denominator so we can point at any JVM and do something useful. e.g. a
stand alone JVM / Tomcat / Jetty/ JBoss / Karaf / Fuse Fabric.
Please consider donating it as Felix WebConsole 5.
Felix can easily reuse it if it wants. Its not Felix / OSGi / Karaf
specific though.
You will change jQuery to Angular.
The default plugins use jQuery and angularjs; though plugins can use
anything they want...
I think hawt.io will finish same as ActiveMQ webconsole. With minimal set of
functionality and problems with security.
Its already got more functionality than the ActiveMQ console & when
deployed in Karaf can reuse the same HTTP security.
Thanks for your feedback!
--
James
-------
Red Hat
Email: jstra...@redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration
