Hi Hadrian, Camel is not only a serve side technology and the added value of a web console makes a lot sense regarding endpoint definition/declaration, routes created / camelContext and certainly for tons of others reasons that I could not explain here. You cannot imagine How helpful it is when we have to present Camel to a customer. With a webconsole, we can immediately display what happen in a camel exchange, the number of exchanges processed, ... and statistics about processing time. This is also true for ActiveMQ and you cannot imagine how much time you win during POC development simply because you can easily show what happen at "what you call" the server side. A web console helps to sell a technology ;-) The web console should be part of Camel 3.0 and we have enough apache talent sto help on CSS, ...
Regards, Charles On Fri, Jan 25, 2013 at 5:57 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > In the context of a few web based consoles available for Camel, including > the Karaf console and the recently announced hawt.io, the question of if > Camel needs its own console popped up. > > My understanding is the some are in favor or Camel continuing to ship with > a web console. My personal opinion is that we should not (starting with > 3.0). > > I understand that a web console is very useful to users and a nice to > have. However, our console is not that great (to put it mildly), not really > maintained and we lack the necessary ui knowledge in the community to > maintain something of excellent quality. I think we should focus on the > server side technology that we do so well. > > Therefore, my personal position and proposal is that we should either move > the console in a subproject or remove it completely. > > Thoughts? > Hadrian > > > -- > Hadrian Zbarcea > Principal Software Architect > Talend, Inc > http://coders.talend.com/ > http://camelbot.blogspot.com/ > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
