In Maven, plugins can be coupled to a Maven lifecycle phase and the configuration can be stored in your pom.xml. This is very convenient if you would like to perform some extra steps when, for example, you are deploying a web application.

But, what if you would like to execute a specific goal of a plugin and use the configuration in your pom.xml?

(more…)

Just spent a costly 30 minutes finding out how to create a tgz tarball on OSX Lion without all the hidden ._ files. These files are the result of using the HFS or HFS+ filesystem.

What I got when issuing a tar -zcvf my-package.tar.gz dir1/ was a structure like this:

1
2
3
4
5
6
7
8
9
10
11

.
._dir1
dir1
  ._file1
  file1
  ._file2
  file2
  ._subdir
  subdir
    ._file3
    file3

When extracting this tarball on Linux, you’ll get all the unnecessary ._ files.

To prevent them from being packaged in the first place, issue the following command from your Terminal: export COPYFILE_DISABLE=true

PS: You could make this setting ‘stick’ by adding them to your ~/.bash_profile

The result now will be a nice and clean tarball:

1
2
3
4
5
6

.
dir1
  file1
  file2
  subdir
    file3

In this post I show you how I setup a little test to see if and how easy I could manage to route the traffic to and from a web service through Mule ESB. The business case for this is an issue that one of our customers ran into when using web services. In a program hundreds of calls are done in a relative short period. Most of the time this isn’t a problem but sometimes vague issues occur. To get a better insight in this issue I want to put Mule in the middle so I can log the request and response and hopefully get a better idea about what is sent across the line. This is called the Web Service Proxy pattern and is commonly used to validate and audit the web service calls. For more background info about this pattern see this article.
(more…)

In my previous post I described how you can setup Spring and Hibernate in combination with the MongoDB. In this post I show you how you can write your unit test for this setup including a workaround for the fact that there isn’t an embedded version of MongoDB.
(more…)

One of the requirements we have for one of our Mule ESB implementations is to log the messages that went through the ESB (especially handy during development and testing). There has been written a lot already about logging with Mule so I am not going to discuss that again. In this post I’ll only show you how you can use Spring/Hibernate and MongoDB to store your messages in the MongoDB, because a document-oriented database like MongoDB is a nice fit for this requirement.
(more…)

In a previous post, I mentioned that you could extend the function library in Altova MapForce and add your own functions. In this post I’ll show you (briefly) how to do this using the Java methods from the previous post.

(more…)

Like I posted before Mulesoft has released a new platform: iPAAS. I just went through the starters guide and I am pretty impressed. Of course the use case in the tutorial is very simple but the whole idea of just putting your Mule config into the cloud and it runs sounds good. And I have seen it working (you can check for yourself by submitting text to this url. (more…)

Mulesoft recently released some new products, totally different from each other but both very welcome.
The first one is MuleStudio. Mule Studio is an Eclipse-based developer tool, that allows to graphically create and test Mule ESB Flows. It is currently in beta but I think it might be a good reason to go back to Eclipse. Last few years I have been using Netbeans for my Mule/Java development because I liked the combination between Netbeans and Maven better.

The other ‘product’ that is released is Mule iON. I think a graphical development tool is nice to have but this iON thing is something that can really become big. It makes you use the cloud as the platform for your integration software. They call it the iPAAS (Integration Platform as a Service).

The coming days I will have a look at both and posts my findings here so stay tuned!

Recently, I ran into an open-source test framework called Citrus. Citrus supports you in testing message interfaces in enterprise applications. Manual testing effort as well as coding mocks and simulators are not necessary. Instead Citrus enables integration testing in an automated way with out-of-the-box simulation of various message transports. We’ll use it to test our Mule based ESB.

Mule, of course, offers great possibility to unit test your application. And we also have a test setup which ‘talks’ to other applications. What we didn’t have was a testing environment which we could use to test the ESB as a blackbox without being dependent on other (external) applications. And this is exactly where Citrus comes in. Citrus makes it possible to test the complete lifecycle of a message flow without being dependent of other systems, actually with Citrus you proxy these dependencies.
In this post I will provide details and tips on how to setup and use Citrus. Although the documentation that is available is easy to read, it is not complete. It took me quite some effort to get it all running but like I said before the benefits of this framework are huge.
(more…)

Although the TcpTunnelerGui has been around for a while (for about 10 years now) it is still helping me out in several situations. The only thing I keep forgetting is where to get it and what the exact syntax is to run it. So for future reference I put it in this post (and hope I remember this post…).

  1. Download the jar (soap-2.3.jar) containing the necessary classes here
  2. Open a command prompt/ terminal and go the location where the jar is located
  3. Run the following command

    4. java -classpath soap-2.3.jar org.apache.soap.util.net.TcpTunnelGui 8081 localhost 8080

For more info about the tunneler see here. So, now when I need this tunneler in the future I know where I can find it and how to use it :-)

Meest gelezen