I knew I solved this problem earlier: I just didn’t know how I solved it. That’s just why wiki’s and blogs are invented.

The problem? One of the developers we’re currently coaching was getting started with the Mule ESB using the book Mule in Action .

When trying to run the Maven-based samples that came with the book, Maven wasn’t able to find the com.sun.jmx:jmxri:1.2.1 and com.sun.jdmk:jmxtools:jar:1.2.1 dependency. Looking at our internal repository, only the related pom.xml appeared to be there (and not the jar).

Continue reading…

Some time ago I already explained how you could use Maven and the jboss-plugin to deploy your war or ear to your JBoss server. Now this works fine as long as your JBoss is a local installation running on the same machine as the one that is running Maven.
Of course there is a big chance that this is not the case in your development environment.
Continue reading…

Although I am using Maven for quite some time now over the last years I have never had the need to create my own archetype. Untill my current project. And luckily this is greatly simplified in Maven2.2.
The first thing to do is to create your ‘base’ module that you want to use as template for your other modules. When this is in place you simply go to the root of your base module and enter:
mvn archetype:create-from-project
After this has successfully completed you go to the directory ‘target/generated-sources/archetype’ and enter the command:
mvn install
And after that you can add the archetype to the catalog in your local repository with the command:
mvn deploy
Continue reading…

In my last post I told about the XSLT processing that I have to do to get the XSD as I wanted it to be. Unfortunately there is not just one XSD that has to be processed but there are actually several of them. And for every change in our CDM (Common Data Model) I had to perform all these transformations by hand. Now that doesn’t feel good so I decided to automate that process. And since we are already heavily using Maven I also wanted to do this with Maven, which actuallly is rather easy to do. I even added a validation step so I can test the created XSD at the same time.
Continue reading…

As I promised here this is the last part about using Maven2 to build, test and deploy an EJB3 application to JBoss5. In part 2 I showed how you can build and deploy your EJB3 application in JBoss. In this step I want to show you how you can (unit)test your EJB3 module before you deploy it to JBoss. In part 2 we had to deploy the bean first, before we could test it, but that is not the most optimal way. It would be nicer if the code is tested before it is deployed to the JBoss server. To do this, I make use of OpenEJB. This is a lightweight container that is very easy to use with Maven. Another advantage of this approach is that the EJB component is tested/used in two different EJB containers and reduces the possiblity that container-specific code is used in the application.
Continue reading…

As I stated here I see three levels of using Maven2 to build and deploy your EJB3 application with JBoss5 as application server. The minimal use of Maven I have described here, in this post I will extend the role of Maven so you can use it for the deployment of the JEE application too. I will also show how to create a client class in Netbeans to test your deployment. To show this I will extend the example I used in the previous post.
Continue reading…

Although I am pretty familair with EJB3 I decided to get prepared for my next certificate SCBCD by going through the book ‘Enterprise JavaBeans 3.0‘ by Burke and Monson-Haefel. A good thing about the book is that they added a ‘workbook’ in which exercises and coding examples are described. However, there is also a ‘disadvantage’ and that is that they use Ant to do the building, deploying and running of the code. And they use JBoss4.0 as an application server, which was the logical choice when the book came out, I guess, but is outdated nowadays. So I decided to rewrite the example a little as an exercise by making use of Maven2 for the building and deploying and do this on JBoss5.0.1 that has been released a few weeks ago.
Continue reading…

Currently I am looking into the possiblities Mule has to offer for our project. One of the things that must be done is to transform a message on our (Tibco) queue to a JAXB object so we can use the object as parameter in our call to an EJB3 bean. How to call a EJB3 bean from Mule I have explained here. In this post I want to show how we setup our JAXB transformer. This transformer isn’t standard available in Mule but, as you will see, it is pretty easy to create your own transformer.
Continue reading…

I have blogged before about how to generate JAXB binding classes based on your WSDL file, this time I wanted to generate JAXB classes based on just XSD files. Although I expected this to be simple, it took me quite some time to get it right, so I decided to give this item its own post :-)
Continue reading…

Like I said here we are evaluating Mule to see if we can use it in our situation. One of the things we must do with Mule is to call our business services that are implemented by EJB3 classes based on a message that was put on a JMS topic. To my surprise this isn’t a standard thing in Mule (the creators of Mule want to be JDK1.4 compliant, so there is no room for standard support EJB3, as far as I understand it).
After some searching I came up with several possible solutions of which I think the next one is the best (at least in our situation):
Continue reading…