The university of Applied Sciences at Brandenburg Germany posted an example they have done. Its a mashup example which gathers online earthquake data from around the world. It then correlates with online weather data from the location of the earthquakes. If it was a major earthquake an alert email is send to personel. The example also exposes restful services listing the earthquakes containing links for more details.
You can read about the example here. And they provide source code in their git repo.
2011-01-26
How to do web service with CXF and ServiceMix webinar series
Adrian Trenaman is having the pleasure of hosting a webinar series on using web services. As far as I can tell there is three different webinars, so there is a lot of details to be covered:
- How to Deploy a Web Service into ServiceMix using CXF
- Using CXF with Camel in ServiceMix
- How to Secure CXF Web Services with SSL/TLS and WS-Security
You can read more about the schedule and register at the FuseSource website. The webinar is free, all you have to do is to register.
Adrian is a solution architect for many years, who have traveld the world, and seen it all at various clients. So he has actually done the stuff he talks about in the real life. So he knows the pains and the gains.
2011-01-09
Looking at example from alternative integration framework
As part of my interrest with integration and Apache Camel, and yes my employment, I keep an eye on Camel alternatives, once in a while.
Recently my twitter search revealed this tweet. Which takes you to a SI Example. Do yourself the favor and check out this example, and return back to this blog post.
Maybe, like me, you started at the sea of XML to try to figure out what the example is trying to tell you? Only by click on the provided diagram to see the larger image, and stare back at the XML for some time you may be able to understand a bit what is happening. Now imagine if there was no image at all, would you be able to understand the integration flow in the example?
If you have Camel experience, wouldn't you think the example could be much simpler and easier to understand, by using Camel? In fact I would say that the Camel DSL would make it out for that image. The Camel DSL would be simple and intuitiv to understand the message flow.
It would be something like this in Camel DSL. Let's pick the XML variation as well.
<route>
<-- this route has 2 inputs -->
<from uri="jms:queue:foo"/>
<from uri="file:somefolder"/>
<-- process splitted message -->
</split>
</route>
Maybe the code comments in the XML is not needed? Can you understand the Camel XML route without the code comments? If so its only 10 lines of XML to define the integration flow.
Recently my twitter search revealed this tweet. Which takes you to a SI Example. Do yourself the favor and check out this example, and return back to this blog post.
Maybe, like me, you started at the sea of XML to try to figure out what the example is trying to tell you? Only by click on the provided diagram to see the larger image, and stare back at the XML for some time you may be able to understand a bit what is happening. Now imagine if there was no image at all, would you be able to understand the integration flow in the example?
If you have Camel experience, wouldn't you think the example could be much simpler and easier to understand, by using Camel? In fact I would say that the Camel DSL would make it out for that image. The Camel DSL would be simple and intuitiv to understand the message flow.
It would be something like this in Camel DSL. Let's pick the XML variation as well.
<route>
<-- this route has 2 inputs -->
<from uri="jms:queue:foo"/>
<from uri="file:somefolder"/>
<-- validate message -->
<to uri="bean:validateService"/> <-- split message ... -->
<split> <-- ... using a method call -->
<method bean="enrichmentService"/><-- process splitted message -->
<to uri="bean:processService"/>
<-- notify splitted message -->
<to uri="bean:notificationService"/><-- notify splitted message -->
</split>
</route>
Maybe the code comments in the XML is not needed? Can you understand the Camel XML route without the code comments? If so its only 10 lines of XML to define the integration flow.
2011-01-05
Camel in Action print book arrived
This is just a short blog entry as a reminder for myself that the Camel in Action print books arrived at my doorstep on January 4th 2011.
 |
| Camel in Action books |
The books actually came on December 28th 2010, but I wasn't home.
The task is done and the book can be closed. I am ready for new adventures.
2011-01-03
Apache Camel - 2010 in numbers
Last year I did this blog post about numbers for 2009, so I thought I should do it again this year.
Just to do a quick post on some of the numbers for the Apache Camel project in year 2010.
Number of releases in 2010: Camel 1.x = 2 releases. Camel 2.x = 4 releases.
Number of posts on Camel user forum in 2010: 6922
Number of commits in 2010: 3936 (commit mails send to public forum).
Total number of tickets created at end of 2010: 3477
Number of tickets created in 2010: 1148 (where as 120 are still unresolved).
Number of tickets resolved in 2010: 1136
Number of tickets updated in 2010: 1840 but still unresolved: 140
Number of unresolved tickets not updated in 2010 or later: 20
I am sure you can dig more numbers if you got the time to hunt them down.
Quickly comparing the numbers with 2009, reveals that the Camel project keeps being very active. We do have a high number of commits, and resolve many tickets. However this year we have a slightly lover number of commits, which most likely is due the fact that in 2009 we where busy working on creating Camel 2.0; and some of the core committers were busy writing a book :)
2011 is going to be a busy year as well, as we will start working on Camel 3.0, soon after we get Camel 2.6 released.
Just to do a quick post on some of the numbers for the Apache Camel project in year 2010.
Number of releases in 2010: Camel 1.x = 2 releases. Camel 2.x = 4 releases.
Number of posts on Camel user forum in 2010: 6922
Number of commits in 2010: 3936 (commit mails send to public forum).
Total number of tickets created at end of 2010: 3477
Number of tickets created in 2010: 1148 (where as 120 are still unresolved).
Number of tickets resolved in 2010: 1136
Number of tickets updated in 2010: 1840 but still unresolved: 140
Number of unresolved tickets not updated in 2010 or later: 20
I am sure you can dig more numbers if you got the time to hunt them down.
Quickly comparing the numbers with 2009, reveals that the Camel project keeps being very active. We do have a high number of commits, and resolve many tickets. However this year we have a slightly lover number of commits, which most likely is due the fact that in 2009 we where busy working on creating Camel 2.0; and some of the core committers were busy writing a book :)
2011 is going to be a busy year as well, as we will start working on Camel 3.0, soon after we get Camel 2.6 released.
Subscribe to:
Posts (Atom)
