In "Final Parameters and Local Variables", Dr. Heinz M. Kabutz rants against
the generalized used of the final keyword in Java code. For him, this is a
"trend' and an "idiotic coding standard".
I'm a firm believer of the complete opposite.
As a software developer, I spend most of my time reasoning about code.
Anything that can make this reasoning easier is welcome. Good practices like
short methods and descriptive names fall in this category. I believe
immutable variables do too.
Immutable variables simplify reasoning because they ensure a stable state
within a scope, whether it's a whole class or a single method. Having
established invariants is a tremendous help in understanding code.
Whether it is with my own code or not, I've experienced time and again that
my mental load was way lower with immutable variables than mutable ones.
Maybe it's just a limitation of m... (more)
To be able to do anything useful, an ESB must be configured with all sorts of
parameters, from endpoint connection URIs to message transformation scripts
to content-based routing definitions. Moreover, ESBs like Mule can host
custom components, which will process messages and perform user-specific
actions on them.
Deploying a new version of an ESB configuration raises the question of
whether it will break anything. How can we build confidence that everything
will be just fine? If unit testing did it for standard software development,
what can it do in the realm of the ESB? Since... (more)
In Mule ESB, outbound dispatching to a destination whose address is known at
runtime only is a pretty trivial endeavor. A less frequent practice consists
in programmatically defining inbound service endpoints.
I recently had to do such thing for a little side project I'm running where
Mule is used as a frontal bus and load throttler in front of a R nodes
exposed over RMI. The goal was to have a non-fixed number of file inbound
endpoints defined in a simple properties file and declare them on a
particular service during the initialization sequence of Mule.
As an integration framewo... (more)
If you want to load Resque's web server on a URL path alongside your main
Ruby on Rails 3 application, no need to mess with config.ru or Rack::URLMap,
as shown in different places.
The solution is way simpler and consists in using the RoR3's capacity to
mount Rack applications directly in the routes table, as shown here:
Yep, it's that simple. Enjoy!
This blog is the formal introduction to the CRaSH console for Mule on which
I've been working for the past month or so. I've decided to interview myself
about it because, hey, if I don't do it, who will?
What is CRaSH for Mule?
It is a shell that is running embedded in Mule and that gives command-line
access to a variety of Mule internal moving parts. It's built thanks to the
excellent CRaSH project, a toolkit built by Julien Viet and sponsored by eXo
Platform, which allows the easy creation of embedded shells.
What can we do with it?
Well, it's easy to find it out. Let's connect ... (more)