You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "michal.warecki" <mi...@gmail.com> on 2012/08/13 14:22:29 UTC

Camel Web Roadmap

Hi!

Is there a roadmap for Camel Web? For many companies, web console is very
important (sometimes obligatory) tool. The current console is functionally
very limited.
If no, I can deal with development of the console. 
At the beginning I would like to take care of the basic context
configuration i.e.:
- thread profiles,
- error handlers,
- data formats.

Next I will try to implement xml configuration persistence. For now, all
changes are made only in runtime.
In the next iteration I will try to create graphical route builder tool.

Do you have any concerns or suggestions? I've created Camel a GIT fork for
this task:
https://github.com/michalwarecki/camel.

Cheers,
Michal





--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel Web Roadmap

Posted by "michal.warecki" <mi...@gmail.com>.
Hi,

I commited an example of two REST resources with html pages which are using
direct JMX client in web console:

- particular thread pool data with "real-time" chart:
http://camel.465427.n5.nabble.com/file/n5717440/threadresource.png 

- table of thread pools data:
http://camel.465427.n5.nabble.com/file/n5717440/threadsresource.png 

- consumers data:
http://camel.465427.n5.nabble.com/file/n5717440/consumersresource.png 

github link:
https://github.com/michalwarecki/camel/tree/trunk/components/camel-web

Currently connectors support only JMX but CamelConnection can be implemented
in multiple ways.

I saw Lars post about using Jolokia as a JMX http proxy but I'm still have
doubts about it. Direct proxy makes REST full-JMX dependent and does not
allow for additions/modifications.

Please review the code and share your comments. If it suites to Camel
assumptions I can modify current resources (endpoint, routes, languages) and
further develop console (i.e. memory monitoring etc.).

Cheers,
Michal



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717440.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel Web Roadmap

Posted by "michal.warecki" <mi...@gmail.com>.
During become familiar with the code of the console, I realized why it has so
few features. Core Camel API does not allow to retrieve all runtime
informations (i.e. ExecutorServiceManager does not allow to retrieve
threadPoolProfiles map).

Fortunatelly Camel management API (JMX) provides a lot of functionalities
that completely meet the requirements of the console. 
If console will be fully based on JMX, there is also possibility to connect
it to remote Camel application. Additionally, you can easily create web
"real-time" charts based on JMX.

In the near future I plan to implement aforementioned functionalities based
on JMX only. If this solution will be worked well, I am pleased that in an
analogous manner to convert the existing code.

What do you think about this solution? Comments are very welcome because it
is you decide on the development of Camel :-)



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717291.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel Web Roadmap

Posted by "michal.warecki" <mi...@gmail.com>.
I think, currently it is impossible to set remote REST host in scalate
templates. It would be nice to deploy html GUI on one machine and REST
services with Camel application on other.



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717241.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel Web Roadmap

Posted by Charles Moulliard <ch...@gmail.com>.
As camel web console already uses REST technology, what do you mean exactly
by (i.e. setting REST services host) ?

On Mon, Aug 13, 2012 at 2:58 PM, michal.warecki <mi...@gmail.com>wrote:

> Hmm, this is a separated project. Do you think whether we can use the code?
> It is based on JMX so it has different architecture than Camel Web. I think
> we can only get some suggestions of functionality like consumers,
> processors
> etc. browsing.
> What do you think? I am also thinking about adding the ability to manage
> Camel remotely by Web (i.e. setting REST services host).
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717238.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com

Re: Camel Web Roadmap

Posted by "michal.warecki" <mi...@gmail.com>.
Hmm, this is a separated project. Do you think whether we can use the code?
It is based on JMX so it has different architecture than Camel Web. I think
we can only get some suggestions of functionality like consumers, processors
etc. browsing.
What do you think? I am also thinking about adding the ability to manage
Camel remotely by Web (i.e. setting REST services host).



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717238.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel Web Roadmap

Posted by Charles Moulliard <ch...@gmail.com>.
Some works have already be done here :
http://sksamuel.github.com/camelwatch/

On Mon, Aug 13, 2012 at 2:22 PM, michal.warecki <mi...@gmail.com>wrote:

> Hi!
>
> Is there a roadmap for Camel Web? For many companies, web console is very
> important (sometimes obligatory) tool. The current console is functionally
> very limited.
> If no, I can deal with development of the console.
> At the beginning I would like to take care of the basic context
> configuration i.e.:
> - thread profiles,
> - error handlers,
> - data formats.
>
> Next I will try to implement xml configuration persistence. For now, all
> changes are made only in runtime.
> In the next iteration I will try to create graphical route builder tool.
>
> Do you have any concerns or suggestions? I've created Camel a GIT fork for
> this task:
> https://github.com/michalwarecki/camel.
>
> Cheers,
> Michal
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com