The Ricston Blog - Life in SOA with the Mule ESB

An Array By Any Other Name

Antoine Borg — Thu, 05 Nov 2009 08:00:08 +0000

With all the recent posts about entry point resolvers, I’ve shown how you can invoke a method based upon a number of techniques like using the method name but in each case, my examples had methods that contained one single input parameter. What if my methods have multiple arguments? In such a case, you can wrap [...]

The Self-Conscious (Mule) Service

Antoine Borg — Mon, 02 Nov 2009 08:00:32 +0000

In the good old days of Mule 1.x, any component that wanted to be aware of its configured state could implement the UMODescriptor interface and get whatever information was needed. This interface is no longer available in Mule 2 but there is a org.mule.api.service.ServiceAware interface that can provide the same sort of information. To investigate [...]

The Method Entry-point-resolver

Antoine Borg — Thu, 29 Oct 2009 08:00:52 +0000

My last entry point resolver (EPR) related post talked about the property-entry-point-resolver which is a great way to specify the name of the method that should be invoked inside a service. There is another way to do this, of course. Instead of using that EPR, you can take advantage of the method-entry-point-resolver and configure things in [...]

Custom Aggregation

Antoine Borg — Mon, 26 Oct 2009 08:00:13 +0000

Have you ever needed to aggregate multiple messages in an inbound router and were not sure exactly how to do this? Stephen Fenech, Consultant at Ricston Ltd, is our guest blogger for today and explains how to do this Recently there were a couple of questions on the user list about custom aggregation. The use case [...]

Null and Null-er

Antoine Borg — Thu, 22 Oct 2009 08:00:08 +0000

When Mule invokes a method that returns a null, is this the same thing as invoking a void method? I didn’t think so and I wanted to write this blog post to document the difference in these two scenarios. Consider the following class: public class MessageFlowClass { public void fullName (String name) { name = "Antoine Borg"; } public [...]

More Entry Point Resolver Fun

Antoine Borg — Mon, 19 Oct 2009 08:00:30 +0000

The standard entry-point resolver automatically determines which method in a class should be invoked. There are cases where a class may have two methods that take the same parameter list and rather than see the TooManySatisfiableMethodsException, it would be great if I could indicate which method to use. This is what the property-entry-point-resolver [...]

The Outbound Flow Stage

Antoine Borg — Thu, 15 Oct 2009 08:00:28 +0000

Many of you who read my post called The Component Flow Stage wondered whether I will write about the next stage; the Outbound Flow Stage. Wonder no more, as here it is The Outbound Flow Stage is the stage invoked once the component flow stage has completed. The method that was invoked should [...]

Using the No-Arguments Entry Point Resolver

Antoine Borg — Mon, 12 Oct 2009 08:00:16 +0000

My previous post on entry point resolvers (EPRs) focused on the Callable EPR but a more useful one if you have pre-existing code is the no-arguments entry point resolver. This will allow Mule to invoke a service method even if the method does not have any parameters. This seems unusual at first glance since we [...]

The Component Flow Stage

Antoine Borg — Thu, 08 Oct 2009 08:00:28 +0000

In a completely asynchronous message flow in Mule, every message is handled by three distinct stages while it passes through a service. Each stage corresponds to a single thread and this is all controlled by the Staged Event Driven Architecture (SEDA) that Mule implements. The inbound flow stage handles the message up until the message [...]

Outbound Patterns for Inbound Routes

Antoine Borg — Mon, 05 Oct 2009 08:00:50 +0000

Interesting question from a class last week: Since splitting is an outbound routing pattern, what should I do if I wish to perform a splitting operation on an inbound route? What if I want to split while receiving messages? One solution would be to create a new Inbound Router and implement the pattern there. This would [...]