Starting Mule Apps from Main Class in Eclipse

This tutorial will show you an example on starting mule apps from main class. You can use any IDE for building your mule apps. Here we will see how to build and start mule apps in Eclipse. You can also use Mule or Anypoint Studio to build your mule apps.

In our previous tutorial we have seen an example on building mule apps with Gradle in Eclipse. Here we will use the previous tutorial to show example on starting mule apps from main class. So basically if you don’t have Anypoint or Mule studio then also you can build your mule apps outside Mule or Anypoint studio.

Continue reading “Starting Mule Apps from Main Class in Eclipse”

Building Mule Apps with Gradle in Eclipse

Building Mule Apps with Gradle in Eclipse, i.e., you are going to create Mule project outside Mule Studio. We will build the Mule project in Eclipse using Gradle script. Gradle is becoming more and more popularity as a build system. It combines the power of scripting with the simplicity of conventions, where customization does not end up in tons of messy configurations. Over the times we have done building Mule apps through Mule Studio using Maven plugin. Here you will create build.gradle script with your own hand to build the Mule project in Eclipse.

Continue reading “Building Mule Apps with Gradle in Eclipse”

Setup Mule, Maven and JDK in Windows

I will show you how to setup Mule, Maven and JDK in Windows environment.

Prerequisites

Mule Studio 3.x(Anypoint Studio) (Download from https://www.mulesoft.com/platform/studio)
Maven 3.2.1 (Download from https://maven.apache.org/download.cgi?Preferred=ftp://mirror.reverse.net/pub/apache/)
JDK 1.7 (Download from http://www.oracle.com/technetwork/java/javase/downloads/index.html)

Continue reading “Setup Mule, Maven and JDK in Windows”

Handling Default Exceptions in Mule

A catch exception strategy can be defined to customize the way Mule handles messages with errors. A catch exception strategy catches all exceptions thrown within its flow and processes them, thereby overriding Mule’s implicit default exception strategy.

Mule’s catch exception strategy behavior is similar to a Java catch block, except that a new exception cannot be thrown or another exception cannot be caught within a catch exception strategy. Continue reading “Handling Default Exceptions in Mule”

Handling Global Exceptions in Mule

A catch exception strategy can be defined to customize the way Mule handles messages with errors. A catch exception strategy catches all exceptions thrown within its flow and processes them, thereby overriding Mule’s implicit default exception strategy.

Mule’s catch exception strategy behavior is similar to a Java catch block, except that a new exception cannot be thrown or another exception cannot be caught within a catch exception strategy. Continue reading “Handling Global Exceptions in Mule”

Handling Local Exceptions in Mule

A catch exception strategy can be defined to customize the way Mule handles messages with errors. A catch exception strategy catches all exceptions thrown within its flow and processes them, thereby overriding Mule’s implicit default exception strategy.

Mule’s catch exception strategy behavior is similar to a Java catch block, except that a new exception cannot be thrown or another exception cannot be caught within a catch exception strategy. Continue reading “Handling Local Exceptions in Mule”

Choice Flow Control in Mule ESB

The choice flow control dynamically routes messages based on message payload or properties. It adds conditional programming to a flow, similar to an if/then/else code block.

A choice flow control uses expressions to evaluate the content of a message, then it routes the message to one of the routing options within its scope. It directs messages to the first routing option in the scope that matches the routing configurations (evaluates to true). If none of expressions evaluate to true, the choice flow control directs the message to the default (else) route. Continue reading “Choice Flow Control in Mule ESB”

Using JMS synchronously in Mule ESB

This tutorial will show you how to use Mule JMS Transport synchronously in Mule based application. As JMS is inherently asynchronous in nature, you will usually use JMS inbound endpoints with one-way message-exchange patterns—sending messages and not waiting around for a response. Sometimes, however, you will want to wait for a response from a message you are sending. You can accomplish this by setting the exchange pattern on a JMS inbound endpoint to request-response.

Continue reading “Using JMS synchronously in Mule ESB”

Sending JMS messages with the JMS outbound endpoint in Mule

This tutorial will show you how to use Mule JMS Transport in Mule based application. Let’s take an example, set up a flow to accept notifications from Accounting application when an expense report’s processing has been completed. A  more realistic use case is to take the notifications and dispatch them to a JMS topic to which interested parties can  subscribe and be notified as expense reports are finalized.

You can be interested in Mule JMS Transport with Active MQ

Continue reading “Sending JMS messages with the JMS outbound endpoint in Mule”