I think one of the most interesting part of hawtio is that the same console can be used in OSGi or in a non-OSGi environment and that's is pluggable with dynamic discovery. That's really what we needed for years, back to the ServiceMix 4 early stage. Having a single console that can adapt multiple deployment environments is really a must-have and that was the problem so far with the current console: we have an activemq and a camel console that work on their own, and a karaf / felix console that only work in OSGi. Having the possibility to unify those is really AWESOME !!!
On Fri, Jan 25, 2013 at 10:48 AM, Charles Moulliard <ch0...@gmail.com>wrote: > - Will check more in depth next week hawt.io and have a look to your > remarks. > - For sure, hawt.io should be the house about camel webconsole and I would > appreciate that everybody fully agree about that idea instead of > continuying to re-invent new webconsole every next major realease of Camel. > - Pertinent remark about command shell and karaf. We will continue this > discussion within Karaf project > > > > > On Fri, Jan 25, 2013 at 10:05 AM, James Strachan > <james.strac...@gmail.com>wrote: > > > On 25 January 2013 08:07, Charles Moulliard <ch0...@gmail.com> wrote: > > > +1 for the project plan and if you are interested I can play the role > of > > > Project Manager to coordinate all the different tasks, actions, define > a > > > plan and > > > following > > > manage it > > > > > > Concerning the webconsole, http://hawt.io project should be the way to > > go > > > (or at least jolokia - http://jolokia.org/ ) even if until now the > code > > is > > > too much javascript, typescript oriented (at my opinion). > > > > You can write hawtio plugins in anything that compiles-to-JS. So use > > pure JS, CoffeeScript, EcmaScript6-transpiler, TypeScript, GWT, > > Kotlin, Ceylon, ClojureScript, ScalaJS or any of the other languages > > that compile to JS: > > http://altjs.org/ > > > > So take your pick; the person who creates a hawtio plugin can use > > whatever language they prefer; so get cracking Charles on a new plugin > > and you can use your preferred language! :) > > > > The only real APIs a plugin needs to worry about are AngularJS (if you > > want to work in the core layout rather than just be an iframe), JSON > > for some pretty trivial extension points like adding new tabs and HTML > > & CSS. We'll probably move to something like RequireJS for dynamic > > module loading at some point; but thats pretty language agnostic > > anyway. > > > > > > > Nevertheless, the webconsole project for Camel should be designed as > > > pluggable, REST based, > > > most probably synchronized with also commands that > > > we have in Karaf (to avoid to duplicate code), packaged as a WAR > > deployable > > > in any Java container (Tomcat, TomEE, Jetty, JEE, Karaf). > > > > That describes hawtio pretty well already. Now we've got hawtio I'm > > not sure why we need another web console project? > > > > The missing bit is reusing karaf commands easily in a web console (as > > they are text console based which isn't ideal); ideally we'd be able > > to introduce an 'object layer' within the commands so that they can > > expose JSON objects before they are turned into text console strings - > > so that a web UI can provide a richer visualisation. > > > > e.g. check the comments on this issue - in particular try watching the > > TermKit demo videos to show the kinds of things a command shell could > > look like in a browser... > > https://github.com/hawtio/hawtio/issues/17 > > > > Though the karaf commands are discussion for the karaf project. > > > > -- > > James > > ------- > > Red Hat > > > > Email: jstra...@redhat.com > > Web: http://fusesource.com > > Twitter: jstrachan, fusenews > > Blog: http://macstrac.blogspot.com/ > > > > Open Source Integration > > > > > > -- > Charles Moulliard > Apache Committer / Sr. Enterprise Architect (RedHat) > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
