It's fascinating this morning to read Steve Chamber's real-time notes on the design of his API. In particular, I was interested in the section on which authentication model to use.
Since the launch of Fuse ESB 7, Fuse MB 7 and in fact the official release of Fuse Fabric, Camel has moved in a new era called "Cloud Integration where machines, services are distributed everywhere.
In the last blog post I introduced Fuse Fabric, an overview of the problems it is intended to solve, and the components that it uses to accomplish pain-free management of large deployments of ActiveMQ and ServiceMix/ESB containers.
The Apache Camel 2.10 release is now available for download from Apache and for Maven users in central maven repo.
An old customer recently asked me if I had a solution for how to integrate between their existing JMS infrastructure on Websphere MQ with RabbitMQ.
FuseSource just recently released enterprise versions of their distributions of ActiveMQ and ServiceMix. Some of the top features include incremental patching, custom platform installers, and third party verification.
This post explains the steps that happen when a Apache CXF developed consumer invokes a remote service and the steps of an interceptor chain.
This week, we're celebrating the 5th anniversary of the Apache Camel project. First, I'll tell you where we mark the "birthdate" of Camel.
This post provides a brief introduction to Switchyard, what it is, and how to use it to build a service-oriented application.
It's pretty awesome when you look back at the 1.0 release of Apache camel and you can see the huge amount of powerful features that were baked into the DNA of the project at such an early stage.
This article concentrates on integration namespace capabilities that have been provided by C24 for building integration flows and, through example, explores the use of C24 iO within those flows.
This morning I woke up to the news out in the public that Red Hat to Acquire FuseSource. This is really great news for the FuseSource team, to find a new home that is truly Open Source down to its DNA.
The motivation for Part 1 of this series was an introduction to C24 iO, a brief explanation of some of it's basic capability and an introduction to iO models used as Spring beans.
This post will breakdown the options that are available today. If you have used other approaches or know of other ongoing development in this area, please let me know.
While looking for real-life case studies of OSGi implementations, I managed to find one of the most high profile deployments. Where? At LinkedIn. Enjoy "Building LinkedIn‘s Next Generation Architecture with OSGi"
RabbitMQ is a message bus built in Erlang. It implements the AMQP protocol, which, unlike JMS, is also a wire protocol and not just an API. Here's a short intro...
How to connect to a remote SLSB from Spring. This method is beautiful. You get an instance of a remote SLSB as a Spring bean. I definitely like it!
Check out this code with some more examples of the magic of WCF.js, the first ws-* implementation for Node.js
The APIs can easily be used to build a web or command line based tool to support remote ActiveMQ management features. That being said, all of these features are available via the JMX console itself and ActiveMQ does provide a web console to support some management/monitoring tasks.
This post gives you a committer's perspective on how the Network Connectors work for Apache ActiveMQ.
The upcoming Apache Camel 2.10 release is on its way. A lot of new components are being added, and two really exiting new components are twitter and websocket.
One company has the best examples gathered from years of experience consulting at various types of clients that focus on the intended way of using the these open source tools. When it comes to wanting to know how to use, for example ServiceMix, and the pitfalls to avoid and best practices to employ, having these docs close at hand is a must.
Apache Camel has a very powerful bean injection framework which allows developers to focus only on solving business problems. However there are situations when you need to do a little bit more. Read below to see how easy it is to setup aspects (AspectJ) in Apache Camel.
I’ve started thinking about the best patterns for implementing error handling in EasyNetQ. One of the aims of EasyNetQ is to remove as many infrastructure concerns from the application developer as possible. This means that the API should correctly handle any exceptions that bubble up from the application layer.