date:20130125

For the impatient just look here :) http://hawt.io/

Background
==
We've had numerous consoles all over the place for some time in
various projects like Felix, Karaf, ActiveMQ, Camel, Tomcat, Fuse
Fabric to name but a few. Many of them quite heavy weight requiring a
custom web app to be deployed (which often is quite large); none
particularly working together.

We've been working on Fuse Fabric and its management console to
provide a more consolidated view of a cluster of Apache integration 
middleware technologies. Increasingly we're seeing our users and
customers using different combinations of technologies in different
containers (e.g. Tomcat + ActiveMQ or Karaf + Camel or Fuse Fabric +
Karaf + ActiveMQ + Camel or whatever).

So for a few months a few of us have been working on trying to make
the various web consoles for things like Apache Camel, ActiveMQ,
Felix/Karaf/OSGi  Fuse Fabric (long with more generic things like JMX
 OSGi) available as lightweight HTML5 plugins so they can be mixed
and matched together to suite any container and combination of
technologies that folks deploy in a JVM.


hawtio
=
The result so far is hawtio: http://hawt.io/

You can deploy it as a WAR in any JVM (or feature in karaf) and it
provides a UI console for whatever it finds in the JVM. So it works
with Tomcat / Jetty / Karaf / JBoss / Fuse Fabric; and has plugins for
JMX, OSGi, ActiveMQ, Camel  Fuse Fabric so far with others on the
way.

The nice thing is its pretty small (about 1Mb WAR containing all the
server side code, HTML, JS, images, CSS etc). The only real server
side component is jolokia which is a small (about 300K) REST connector
for JMX (which is awesome BTW!) - the rest is static content (which
could be served from anywhere so doesn't need to be deployed in each
JVM).

Its based around a plugin architecture:
http://hawt.io/developers/plugins.html

so its easy to add new plugins for any kind of technology. A plugin is
pretty much anything that runs in a browser.

The nice thing is hawtio can discover UI plugins at runtime by
examining the contents of the JVM or querying REST endpoints; so the
UI can update in real time as you deploy new things into a JVM!


hawtio, the hawt camel rider
==
A quick summary of the current features for camel folks:

* If you have any camel contexts running in a JVM when hawtio starts
up it adds an Integration tab which shows all the camel contexts
running.

* You can start/stop/suspend/resume the context and its routes; then
look at all the metrics for routes/endpoints/processors. The Charts
tab lets you visualise the real time metrics.

* You can create new endpoints; browse endpoints which are browsable 
send messages to endpoints (with syntax editing support for JSON / XML
/ YAML / properties)

* You can visualise all the camel routes or a specific camel route for
a context in the Diagram tab and see real time metrics of how many
messages are passing through each step on the diagram. e.g.
https://raw.github.com/hawtio/hawtio/master/website/src/images/screenshots/camelRoute.png

* Clicking on a Route allows you to Trace it; when tracing if you send
a message into a route then it captures a copy of the message at each
point through the route. So you can step through (scroll/click through
the table) a route and see the message contents and how the message
flows through the EIPs - highlighting where on the diagram each
message is. This is very handy for figuring out why your route doesn't
work :) Spot where the heading disappears! Or see why the CBR doesn't
go where you expected.

In general most of the runtime features of the open source Fuse IDE
eclipse tooling are now supported in the camel hawtio plugin; so
available in a web browser.


Summary
===
So if you're vaguely interested in web consoles for Apache Camel I
urge you to give it a try. We love contributions and feedback!
http://hawt.io/contributing/index.html

or feel free to raise new issues for how to improve the camel plugin:
https://github.com/hawtio/hawtio/issues?labels=camelpage=1sort=updatedstate=open

or if you've an itch for a new kind of plugin please dive in! We
should be able to expose existing web apps/consoles as links inside
hawtio too BTW.

Feedback appreciated! Its hawt, but stay cool! ;)

--
James
---
Red Hat

Email: jstra...@redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/

Open Source Integration

Eclipse Plugin Production Build

2013-01-25 Thread sammm

i've got a question about building production releases when the content XML
file is setup for the Eclipse. I have (in my POM) moved the 'camel-eclipse'
plugin to a separate profile which i only reference in an Eclipse run
configuration.
The trouble is, however, that i therefore need a way to [conditionally]
exclude this bean:

bean id=eclipseResolver
class=org.apache.camel.component.eclipse.EclipsePackageScanClassResolver/

i.e., if i'm running in eclipse i want the bean but if i'm building a
production release then i dont want that bean in the XML as it causes class
errors when deployed to ServiceMix.

Is there a way when running using the 'camel:run' mvn target to specify a
different XML file to use?

Martin




--
View this message in context: 
http://camel.465427.n5.nabble.com/Eclipse-Plugin-Production-Build-tp5726247.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

2013-01-25 Thread Martin Stiborský

Hello,
it looks really nice…I just give it a try, trying to install it in Karaf,
where is my Camel project running, but after ~50 minut I wasn't succesfull.
I was trying to utilize Fuse features.xml, to install hawtio, but that
wasn't probably good idea :)
I'll come back to it later, but if there is a easy way how to install
hawtio as OSGi bundle into Apache Karaf, let me know, please.
I'm still new in those things, so most probably I just did something wrong,
or over-complicated :)

On Fri, Jan 25, 2013 at 10:59 AM, James Strachan
james.strac...@gmail.comwrote:

For the impatient just look here :) http://hawt.io/

Background
==
We've had numerous consoles all over the place for some time in
various projects like Felix, Karaf, ActiveMQ, Camel, Tomcat, Fuse
Fabric to name but a few. Many of them quite heavy weight requiring a
custom web app to be deployed (which often is quite large); none
particularly working together.

We've been working on Fuse Fabric and its management console to
provide a more consolidated view of a cluster of Apache integration
middleware technologies. Increasingly we're seeing our users and
customers using different combinations of technologies in different
containers (e.g. Tomcat + ActiveMQ or Karaf + Camel or Fuse Fabric +
Karaf + ActiveMQ + Camel or whatever).

So for a few months a few of us have been working on trying to make
the various web consoles for things like Apache Camel, ActiveMQ,
Felix/Karaf/OSGi Fuse Fabric (long with more generic things like JMX
OSGi) available as lightweight HTML5 plugins so they can be mixed
and matched together to suite any container and combination of
technologies that folks deploy in a JVM.

hawtio
=
The result so far is hawtio: http://hawt.io/

You can deploy it as a WAR in any JVM (or feature in karaf) and it
provides a UI console for whatever it finds in the JVM. So it works
with Tomcat / Jetty / Karaf / JBoss / Fuse Fabric; and has plugins for
JMX, OSGi, ActiveMQ, Camel Fuse Fabric so far with others on the
way.

The nice thing is its pretty small (about 1Mb WAR containing all the
server side code, HTML, JS, images, CSS etc). The only real server
side component is jolokia which is a small (about 300K) REST connector
for JMX (which is awesome BTW!) - the rest is static content (which
could be served from anywhere so doesn't need to be deployed in each
JVM).

Its based around a plugin architecture:
http://hawt.io/developers/plugins.html

so its easy to add new plugins for any kind of technology. A plugin is
pretty much anything that runs in a browser.

The nice thing is hawtio can discover UI plugins at runtime by
examining the contents of the JVM or querying REST endpoints; so the
UI can update in real time as you deploy new things into a JVM!

hawtio, the hawt camel rider
==
A quick summary of the current features for camel folks:

* If you have any camel contexts running in a JVM when hawtio starts
up it adds an Integration tab which shows all the camel contexts
running.

* You can start/stop/suspend/resume the context and its routes; then
look at all the metrics for routes/endpoints/processors. The Charts
tab lets you visualise the real time metrics.

* You can create new endpoints; browse endpoints which are browsable
send messages to endpoints (with syntax editing support for JSON / XML
/ YAML / properties)

* You can visualise all the camel routes or a specific camel route for
a context in the Diagram tab and see real time metrics of how many
messages are passing through each step on the diagram. e.g.

https://raw.github.com/hawtio/hawtio/master/website/src/images/screenshots/camelRoute.png

* Clicking on a Route allows you to Trace it; when tracing if you send
a message into a route then it captures a copy of the message at each
point through the route. So you can step through (scroll/click through
the table) a route and see the message contents and how the message
flows through the EIPs - highlighting where on the diagram each
message is. This is very handy for figuring out why your route doesn't
work :) Spot where the heading disappears! Or see why the CBR doesn't
go where you expected.

In general most of the runtime features of the open source Fuse IDE
eclipse tooling are now supported in the camel hawtio plugin; so
available in a web browser.

Summary
===
So if you're vaguely interested in web consoles for Apache Camel I
urge you to give it a try. We love contributions and feedback!
http://hawt.io/contributing/index.html

or feel free to raise new issues for how to improve the camel plugin:

https://github.com/hawtio/hawtio/issues?labels=camelpage=1sort=updatedstate=open

or if you've an itch for a new kind of plugin please dive in! We
should be able to expose existing web apps/consoles as links inside
hawtio too BTW.

Feedback appreciated! Its hawt, but stay cool! ;)

--
James
---
Red Hat

Email:

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

If the feature file doesn't work you could just try this:

* add this line to your etc/org.ops4j.pax.url.mvn.cfg (which won't be
needed once we've released 1.0 soon ;)

org.ops4j.pax.url.mvn.repositories= \
 
https://oss.sonatype.org/content/repositories/snapshots=sonatype.snapshot.repo
\

* then in the Karaf / Fuse ESB console try:

   features:install war
   install mvn:io.hawt/hawtio-web/1.0-SNAPSHOT/war


On 25 January 2013 11:32, Martin Stiborský martin.stibor...@gmail.com wrote:
 Hello,
 it looks really nice…I just give it a try, trying to install it in Karaf,
 where is my Camel project running, but after ~50 minut I wasn't succesfull.
 I was trying to utilize Fuse features.xml, to install hawtio, but that
 wasn't probably good idea :)
 I'll come back to it later, but if there is a easy way how to install
 hawtio as OSGi bundle into Apache Karaf, let me know, please.
 I'm still new in those things, so most probably I just did something wrong,
 or over-complicated :)


 On Fri, Jan 25, 2013 at 10:59 AM, James Strachan
 james.strac...@gmail.comwrote:

 For the impatient just look here :) http://hawt.io/

 Background
 ==
 We've had numerous consoles all over the place for some time in
 various projects like Felix, Karaf, ActiveMQ, Camel, Tomcat, Fuse
 Fabric to name but a few. Many of them quite heavy weight requiring a
 custom web app to be deployed (which often is quite large); none
 particularly working together.

 We've been working on Fuse Fabric and its management console to
 provide a more consolidated view of a cluster of Apache integration 
 middleware technologies. Increasingly we're seeing our users and
 customers using different combinations of technologies in different
 containers (e.g. Tomcat + ActiveMQ or Karaf + Camel or Fuse Fabric +
 Karaf + ActiveMQ + Camel or whatever).

 So for a few months a few of us have been working on trying to make
 the various web consoles for things like Apache Camel, ActiveMQ,
 Felix/Karaf/OSGi  Fuse Fabric (long with more generic things like JMX
  OSGi) available as lightweight HTML5 plugins so they can be mixed
 and matched together to suite any container and combination of
 technologies that folks deploy in a JVM.


 hawtio
 =
 The result so far is hawtio: http://hawt.io/

 You can deploy it as a WAR in any JVM (or feature in karaf) and it
 provides a UI console for whatever it finds in the JVM. So it works
 with Tomcat / Jetty / Karaf / JBoss / Fuse Fabric; and has plugins for
 JMX, OSGi, ActiveMQ, Camel  Fuse Fabric so far with others on the
 way.

 The nice thing is its pretty small (about 1Mb WAR containing all the
 server side code, HTML, JS, images, CSS etc). The only real server
 side component is jolokia which is a small (about 300K) REST connector
 for JMX (which is awesome BTW!) - the rest is static content (which
 could be served from anywhere so doesn't need to be deployed in each
 JVM).

 Its based around a plugin architecture:
 http://hawt.io/developers/plugins.html

 so its easy to add new plugins for any kind of technology. A plugin is
 pretty much anything that runs in a browser.

 The nice thing is hawtio can discover UI plugins at runtime by
 examining the contents of the JVM or querying REST endpoints; so the
 UI can update in real time as you deploy new things into a JVM!


 hawtio, the hawt camel rider
 ==
 A quick summary of the current features for camel folks:

 * If you have any camel contexts running in a JVM when hawtio starts
 up it adds an Integration tab which shows all the camel contexts
 running.

 * You can start/stop/suspend/resume the context and its routes; then
 look at all the metrics for routes/endpoints/processors. The Charts
 tab lets you visualise the real time metrics.

 * You can create new endpoints; browse endpoints which are browsable 
 send messages to endpoints (with syntax editing support for JSON / XML
 / YAML / properties)

 * You can visualise all the camel routes or a specific camel route for
 a context in the Diagram tab and see real time metrics of how many
 messages are passing through each step on the diagram. e.g.

 https://raw.github.com/hawtio/hawtio/master/website/src/images/screenshots/camelRoute.png

 * Clicking on a Route allows you to Trace it; when tracing if you send
 a message into a route then it captures a copy of the message at each
 point through the route. So you can step through (scroll/click through
 the table) a route and see the message contents and how the message
 flows through the EIPs - highlighting where on the diagram each
 message is. This is very handy for figuring out why your route doesn't
 work :) Spot where the heading disappears! Or see why the CBR doesn't
 go where you expected.

 In general most of the runtime features of the open source Fuse IDE
 eclipse tooling are now supported in the camel hawtio plugin; so
 available in a web browser.


 Summary
 ===
 So if you're vaguely interested in web consoles for Apache Camel I

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

2013-01-25 Thread Łukasz Dywicki

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. There was example how to use it together with
Camel and ServiceMix. But you never took time to take a look on that. You
decided to create another project instead of supporting existing Apache
community project. Or, I should be happy that you did not fork it?

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. If I
remember correctly that's third console you produced for Fabric (I don't count
previous Fuse consoles). I hope it will be latest and you will not drop the
idea and continue supporting it.
Hawt.io structure (because is has no architecture) is same as Felix WebConsole.
In comparision Felix console uses OSGi services, your uses JMX. Please consider
donating it as Felix WebConsole 5. You will change jQuery to Angular. I think
hawt.io will finish same as ActiveMQ webconsole. With minimal set of
functionality and problems with security.

Cheers,
Lukasz
--
Small discamler: it's my personal opinion. I do not represent any company here.

Wiadomość napisana przez James Strachan james.strac...@gmail.com w dniu 25
sty 2013, o godz. 10:59:

For the impatient just look here :) http://hawt.io/

hawtio
=
The result so far is hawtio: http://hawt.io/

Its based around a plugin architecture:
http://hawt.io/developers/plugins.html

so its easy to add new plugins for any kind of technology. A plugin is
pretty much anything that runs in a browser.

The nice thing is hawtio can discover UI plugins at runtime by
examining the contents of the JVM or querying REST endpoints; so the
UI can update in real time as you deploy new things into a JVM!

hawtio, the hawt camel rider
==
A quick summary of the current features for camel folks:

* If you have any camel contexts running in a JVM when hawtio starts
up it adds an Integration tab which shows all the camel contexts
running.

* You can start/stop/suspend/resume the context and its routes; then
look at all the metrics for routes/endpoints/processors. The Charts
tab lets you visualise the real time metrics.

* You can create new endpoints; browse endpoints which are browsable
send messages to endpoints (with syntax editing support for JSON / XML
/ YAML / properties)

* You can visualise all the camel routes or a specific camel route for
a context in the Diagram tab and see real time metrics of how many
messages are passing through each step on the diagram. e.g.
https://raw.github.com/hawtio/hawtio/master/website/src/images/screenshots/camelRoute.png

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

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

Re: Camel Routing using Java DSL in Servlet without Spring

2013-01-25 Thread CamelNewbieUser

Hi,

I tried to find release date for Apache Camel 2.11 but it is nowhere
mentioned.
Also the links provided on the  site
http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.11.0/apache-camel-2.11.0.zip
  
is showing HTTP 404.

I tried to download the SNAPSHOT version and build using Maven but facing
difficulties.

It would be better to have SC release.

Can please help with tentative dates for the RC?

Thanks in advance,
Manoj



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Routing-using-Java-DSL-in-Servlet-without-Spring-tp5725880p5726239.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Multiple POST parameters in Spring DSL

2013-01-25 Thread CamelNewbieUser

Hello,

I am currently facing issue with passing multiple POST parameters from html
page to servlet and routed to Camel Spring DSL.





camel:from uri=servlet:///getPOI?matchOnUriPrefix=true/
 camel:setHeader headerName=CamelHttpMethod
inheritErrorHandler=true
camel:constantPOST/camel:constant
/camel:setHeader

camel:setHeader headerName=Content-Type 
inheritErrorHandler=true
   
camel:constantapplication/x-www-form-urlencoded/camel:constant
/camel:setHeader
camel:setBody inheritErrorHandler=true

camel:simpleuserID=${header.userID},password=${header.password},poiID=${header.poiID}/camel:simple
 /camel:setBody
 camel:choice
camel:when
camel:method bean=testbean method=checkParameters/
camel:to
uri=http://localhost:8080/ReceiveParameters/ReceiveServlet?bridgeEndpoint=trueamp;throwExceptionOnFailure=false;
inheritErrorHandler=true pattern=InOnly/

/camel:when
camel:otherwise
camel:to
uri=http://localhost:8080/ReceiveParameters/ReceiveServlet?bridgeEndpoint=trueamp;throwExceptionOnFailure=false;
inheritErrorHandler=true pattern=InOnly/
/camel:otherwise
/camel:choice
/camel:route



How to separate the parameters in setBody CamelContext?




camel:setBody inheritErrorHandler=true

camel:simpleuserID=${header.userID},password=${header.password},poiID=${header.poiID}/camel:simple



Currently all the parameters are being received as single parameter 
userID=uid-12345,password=uid-12345,poiID=Pune
 and I tried to use SPLIT, with , as tokenizer 
camel:splitcamel:tokenize token=,//camel:split
 but still it is not working.


Please suggest.

Thanks in advance,
Manoj



--
View this message in context: 
http://camel.465427.n5.nabble.com/Multiple-POST-parameters-in-Spring-DSL-tp5726242.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

2013-01-25 Thread Preben.Asmussen

Gave it a ride to test it and it looks awesome. 
http://camel.465427.n5.nabble.com/file/n5726252/hawt.io.png 

Still prefer VisualVM when it comes to monitoring though. Besides JMX
threads, CPU and mem can be accessed here too.

More feedback to come later when I get some more time.

/Preben




--
View this message in context: 
http://camel.465427.n5.nabble.com/ANN-hawtio-a-new-lightweight-HTML5-console-for-Apache-Camel-ActiveMQ-JMX-OSGi-Fuse-Fabric-tp5726244p5726252.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

On 25 January 2013 12:58, Preben.Asmussen p...@dr.dk wrote:
 Gave it a ride to test it and it looks awesome.
 http://camel.465427.n5.nabble.com/file/n5726252/hawt.io.png

Thanks!


 Still prefer VisualVM when it comes to monitoring though. Besides JMX
 threads, CPU and mem can be accessed here too.

Yeah, am sure we can improve the JMX monitoring some more with some
nicer views. We maybe need a kinda 'system' view showing CPU / memory
/ threads / disk in a simpler single view.

FWIW the JMX tab if you select java.lang you can view/chart metrics
on OperationSystem / Threading though the Memory stuff could use some
work though.


 More feedback to come later when I get some more time.

Thanks!

--
James
---
Red Hat

Email: jstra...@redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/

Open Source Integration

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

Lukasz, I'm sorry you're angry, but you're missing the point that the Karaf
web console is bound to OSGi even if it can be reused with Camel or
ActiveMQ.
So the Camel and ActiveMQ community will never drop their own console,
because the OSGi users is only a fraction of the user base.  Hawtio enable
all projects to cooperate on a single web console, at last.
So it serves a more general purpose imnsho.

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

2013-01-25 Thread Łukasz Dywicki

I'm not angry. I'm just telling the truth. Nobody told to you yet. Why you 
think it's bound to OSGi? We have WAR packaging. Overall destination was always 
to support other runtimes. Charles was talking about that and he found even a 
name for it once it will get TLP (Orion). But it was so long ago you propably 
don't remember.

Cheers, :)
Lukasz


Wiadomość napisana przez Guillaume Nodet gno...@gmail.com w dniu 25 sty 2013, 
o godz. 14:08:

 Lukasz, I'm sorry you're angry, but you're missing the point that the Karaf
 web console is bound to OSGi even if it can be reused with Camel or
 ActiveMQ.
 So the Camel and ActiveMQ community will never drop their own console,
 because the OSGi users is only a fraction of the user base.  Hawtio enable
 all projects to cooperate on a single web console, at last.
 So it serves a more general purpose imnsho.

Re: Scala DSL with Scala 2.10

2013-01-25 Thread Alexander Nemish

Henryk Konsek hekonsek@... writes:

 
  I have logged ticket
  https://issues.apache.org/jira/browse/CAMEL-6011
 
  And upgrading Scala now.
 
 Actually this is not a Scala-way to just upgrade the version of the library.
 
 In fact we should create separated module for 2.10 (cloned from the
 2.9). New development should take place in 2.10 module while existing
 2.9 module should be kept for the compatibility reasons.
 
 Now we force people who want to switch from Camel 2.10 to Camel 2.11
 to migrate all their business code to Scala 2.10 as well. And this can
 be painful for them.
 
 I can handle this issue if you want, but I strongly recommend to keep
 Scala 2.9 support.
 
 

Totally agree. The Scala way to do is to build and publish camel-scala_2.9.2-
2.11.0.jar and camel-scala_2.10-2.11.0.jar so sbt could manage scala version 
automatically. You may want to check http://www.scala-
sbt.org/release/docs/Getting-Started/Library-Dependencies.html#getting-the-
right-scala-version-with

Cheers,
Alexander Nemish

Re: Camel Routing using Java DSL in Servlet without Spring

2013-01-25 Thread Claus Ibsen

On Fri, Jan 25, 2013 at 10:46 AM, CamelNewbieUser
harddrive.ma...@gmail.com wrote:
 Hi,

 I tried to find release date for Apache Camel 2.11 but it is nowhere
 mentioned.
 Also the links provided on the  site
 http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.11.0/apache-camel-2.11.0.zip
 is showing HTTP 404.

 I tried to download the SNAPSHOT version and build using Maven but facing
 difficulties.

 It would be better to have SC release.

 Can please help with tentative dates for the RC?


Sometime next month is the current ETA.


 Thanks in advance,
 Manoj



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Routing-using-Java-DSL-in-Servlet-without-Spring-tp5725880p5726239.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel Routing using Java DSL in Servlet without Spring

2013-01-25 Thread Claus Ibsen

On Fri, Jan 25, 2013 at 10:46 AM, CamelNewbieUser
harddrive.ma...@gmail.com wrote:
 Hi,

 I tried to find release date for Apache Camel 2.11 but it is nowhere
 mentioned.
 Also the links provided on the  site
 http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.11.0/apache-camel-2.11.0.zip
 is showing HTTP 404.

 I tried to download the SNAPSHOT version and build using Maven but facing
 difficulties.

 It would be better to have SC release.

 Can please help with tentative dates for the RC?


You can see the JIRA roadmap for ETA dates
https://issues.apache.org/jira/browse/CAMEL#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

 Thanks in advance,
 Manoj



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Routing-using-Java-DSL-in-Servlet-without-Spring-tp5725880p5726239.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Getting next JMS Message before Route is Suspended

2013-01-25 Thread wxkevin

I have read several posts on suspending routes such as
http://camel.465427.n5.nabble.com/Suspend-route-what-about-the-current-exchange-td5545837.html
and have read
https://camel.apache.org/how-can-i-stop-a-route-from-a-route.html.

The problem I am having is that in the time that it takes to spawn a new
thread and suspend the route, sometimes the next JMS message will be
consumed which I don't want to happen. The message I receive that causes me
to pause the route kicks off another process. When that process finishes I
send a resume command to the route to continue processing off the JMS Queue.
I need this to happen in exactly this order. I cannot read the next message
and act upon it until the other processes has finished.

Any suggestions?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Getting-next-JMS-Message-before-Route-is-Suspended-tp5726262.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Overload CamelContextFactoryBean

2013-01-25 Thread Benjamin Graf

Hi,

does anybody knows a way to overload/extend the spring osgi implementation of 
CamelContextFactoryBean? I actually wants to extend the basic implementation to 
do some further magic. :-) There seems to be some tricky ways to do it with an 
own SpringNamespaceHandler and extending the camel-spring.xsd but I failed so 
far. :-(

Thx for any help
Benjamin

Re: File component - run them sequentially

2013-01-25 Thread Claus Ibsen

On Fri, Jan 25, 2013 at 3:38 PM, renamsavio renamsav...@gmail.com wrote:
 Does someone have any idea how to solve it?


You can use the API on CamelContext to start|stop routes. So you would
need to figure out
when there is no more files on route1, to start route2, and so forth.
And what should happen when route 3 is done. Should it start route1.
So it goes in round robin?

You can enable the sendEmptyMessageWhenIdle=true, which will have an
empty message being sent out in the route.
Then you can use that to know that there is no more file, and then
start the next route
http://camel.apache.org/how-can-i-stop-a-route-from-a-route.html

In Camel 2.11 it may be a bit easier with the control bus eip
http://camel.apache.org/controlbus.html

You can also use on completion
http://camel.apache.org/oncompletion.html

That may be easier. The file consumer is batch consumer, so there is a
special header that tells when the batch is done = no more files.
Then in the on consumer you can filter on that, and react upon
stopping current route, and start next.




 Thanks!



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/File-component-run-them-sequentially-tp5726185p5726264.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

On Fri, Jan 25, 2013 at 2:36 PM, Łukasz Dywicki l...@code-house.org wrote:

 I'm not angry. I'm just telling the truth. Nobody told to you yet.


Thx for that,  I think I was really erring on the dark side before ;-)


 Why you think it's bound to OSGi? We have WAR packaging.  Overall
 destination was always to support other runtimes.


The war packaging does start an OSGi framework inside the war.  In addition
the console heavily depends on pax-wicket, which afaik, does need OSGi.  As
you said, injection is done through OSGi services.  My understanding (feel
free to correct me if I'm wrong) is that the camel plugins is injected with
a list of CamelContext coming from OSGi.  Which kinda means to me, that you
need to deploy your camel contexts in OSGi, next to the console itself.


 Charles was talking about that and he found even a name for it once it
 will get TLP (Orion). But it was so long ago you propably don't remember.


Maybe I missed something, but when the Orion proposal was raised, Karaf web
console did not really exist yet.

The proposal was to create a TLP for an OSGi web console with a real web
framework.   None of these ideas did sound good to me at that time (having
a TLP for an OSGi web console and rewriting the existing webconsole with a
web framework).  We disagree, but these 2 years did not really changed my
mind.
Now, a few people went ahead and rewrote an OSGi based web console, which
is nice, but it's still is an OSGi web console and I still don't like the
technical design decisions that were taken.

And more importantly, this console does not really help half of our camel
users which do not use OSGi.



 Cheers, :)


Np.  We've been trying to get the webconsole problems fixed since the
beginning with ServiceMix 3, so that's almost 6 years ago now.  it became
even more complicated with ServiceMix 4 switching to OSGi.  I think we have
a clean solution now that can work for all projects with hawtio.
Will the project last and pick up ? No one knows yet.  Not all projects are
bound to suceed.  The one that do usually solves real problems in a clean
way.  I think hawtio is a good bet now ... until someone comes up with a
better project.  That's how it works.


 Lukasz


 Wiadomość napisana przez Guillaume Nodet gno...@gmail.com w dniu 25 sty
 2013, o godz. 14:08:

  Lukasz, I'm sorry you're angry, but you're missing the point that the
 Karaf
  web console is bound to OSGi even if it can be reused with Camel or
  ActiveMQ.
  So the Camel and ActiveMQ community will never drop their own console,
  because the OSGi users is only a fraction of the user base.  Hawtio
 enable
  all projects to cooperate on a single web console, at last.
  So it serves a more general purpose imnsho.




-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

I personally find the tone of this exchange very distasteful and I would 
much appreciate you continuing it on other media channels than the 
@camel user lists.


FWIW, Lukasz made some valid points. However, you saw a need for a new 
project, created it, great. Hawt.io is nice, please continue to drive 
its development there.


Thanks,
Hadrian



On 01/25/2013 07:36 AM, James Strachan wrote:

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

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

This is one more reason why the hawt.io discussions should take place in 
the hawt.io communities. Not here.


Thanks,
Hadrian

On 01/25/2013 08:08 AM, Guillaume Nodet wrote:

Lukasz, I'm sorry you're angry, but you're missing the point that the Karaf
web console is bound to OSGi even if it can be reused with Camel or
ActiveMQ.
So the Camel and ActiveMQ community will never drop their own console,
because the OSGi users is only a fraction of the user base.  Hawtio enable
all projects to cooperate on a single web console, at last.
So it serves a more general purpose imnsho.

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

You misunderstood me.  So I rephrase.

Camel and ActiveMQ community needs a versatile console which can run in a
non OSGi environement, so they can't drop their current web console in
favor of the karaf one.

This discussion is imho totally relevant for the camel community, as it is
for all other projects.  I already forwarded the email to the karaf
community and other projects may be involved too.



On Fri, Jan 25, 2013 at 4:24 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:

 This is one more reason why the hawt.io discussions should take place in
 the hawt.io communities. Not here.

 Thanks,
 Hadrian


 On 01/25/2013 08:08 AM, Guillaume Nodet wrote:

 Lukasz, I'm sorry you're angry, but you're missing the point that the
 Karaf
 web console is bound to OSGi even if it can be reused with Camel or
 ActiveMQ.
 So the Camel and ActiveMQ community will never drop their own console,
 because the OSGi users is only a fraction of the user base.  Hawtio enable
 all projects to cooperate on a single web console, at last.
 So it serves a more general purpose imnsho.




-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Persisting route details..

2013-01-25 Thread Vishal Changrani

Hi,

There are a couple of use-cases that I want to address -
1. Persisting all routes last start-time and end-time somehow so that on the 
application server startup routes do not start if they have just recently ran 
and also to report route statistics.
2.Modifying the routes such that the changes don't take effect untill the 
current exchange finishes.

Can anyone share their insights if they have done something similar?
I have Camel running in Jboss with Oracle at the backend. I was thinking of 
creating a table - route_status to persist all this information but was 
wondering if there is a better approach.

Thanks,
V

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric

Ok, that is a different discussion I would rather have in the context of 
Camel 3.0. I will start a separate thread for this. Having the 
conversation in the context of the subject of this thread may be 
confusing. Sorry for the misunderstanding.


Cheers,
Hadrian


On 01/25/2013 10:42 AM, Guillaume Nodet wrote:

You misunderstood me.  So I rephrase.

Camel and ActiveMQ community needs a versatile console which can run in a
non OSGi environement, so they can't drop their current web console in
favor of the karaf one.

This discussion is imho totally relevant for the camel community, as it is
for all other projects.  I already forwarded the email to the karaf
community and other projects may be involved too.



On Fri, Jan 25, 2013 at 4:24 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:


This is one more reason why the hawt.io discussions should take place in
the hawt.io communities. Not here.

Thanks,
Hadrian


On 01/25/2013 08:08 AM, Guillaume Nodet wrote:


Lukasz, I'm sorry you're angry, but you're missing the point that the
Karaf
web console is bound to OSGi even if it can be reused with Camel or
ActiveMQ.
So the Camel and ActiveMQ community will never drop their own console,
because the OSGi users is only a fraction of the user base.  Hawtio enable
all projects to cooperate on a single web console, at last.
So it serves a more general purpose imnsho.

Re: Persisting route details..

Camel currently is essentially stateless. You can achieve what you want, 
but you'd have to implement it yourself. Something along the lines you 
mentioned.


We are however planning to have support for persistence at a core level 
in 3.0. Christian Ohr added some details about that on the 3.0 ideas 
page [1] (near the bottom of the page).


[1] http://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Ideas

Cheers
Hadrian

On 01/25/2013 10:56 AM, Vishal Changrani wrote:

Hi,

There are a couple of use-cases that I want to address -
1. Persisting all routes last start-time and end-time somehow so that on the 
application server startup routes do not start if they have just recently ran 
and also to report route statistics.
2.Modifying the routes such that the changes don't take effect untill the 
current exchange finishes.

Can anyone share their insights if they have done something similar?
I have Camel running in Jboss with Oracle at the backend. I was thinking of 
creating a table - route_status to persist all this information but was 
wondering if there is a better approach.

Thanks,
V

Re: Scala DSL with Scala 2.10

2013-01-25 Thread Henryk Konsek

 Totally agree. The Scala way to do is to build and publish camel-scala_2.9.2-
 2.11.0.jar and camel-scala_2.10-2.11.0.jar

I reopened the Scala 2.10 issue [1] so we might settle an agreement on
how Scala backwards compatibility should be handled in Camel.

+1 for renaming existing Scala module to camel-scala_2.9.2 and
creating new camel-scala_2.10 module (by cloning).

[1] https://issues.apache.org/jira/browse/CAMEL-6011

--
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi Fuse Fabric