 |
|||
Pragmatic Integrators |
|||
| 2 March |
XML is quite common nowadays, especially in the application integration business that I am involved in. However, I still see companies making big mistakes when they decide to start using XML (for example as the exchange format with their business partners). This series of posts is about mistakes (or at least clumsiness) in using XML that I noticed during several projects. Not making (useful) use of namespaces |
| 24 February |
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 |
| 23 February |
Refactoring code is part of daily business for any programmer. Recently, I’ve discovered http://refactormycode.com/. Haven’t used it yet, but I thought I’d share this gem. You have the possibility to describe the challenge you’re facing, copy-and-paste any (relevant) code and then … you wait. Brilliant! A very nice example of involving the community when refactoring your next piece of software. |
| 9 February |
XML is quite common nowadays, especially in the application integration business that I am involved in. However, I still see companies making big mistakes when they decide to start using XML (for example as the exchange format with their business partners). This series of posts is about mistakes (or at least clumsiness) in using XML that I noticed during several projects. Only change the syntax of the CSV file (no normalization) |
| 7 February |
XML is quite common nowadays, especially in the application integration business that I am involved in. However, I still see companies making big mistakes when they decide to start using XML (for example as the exchange format with their business partners). This post is about one of the mistakes I noticed during one of my projects. Not using a schema (XSD) or DTD |
| 12 January |
I needed Mule to determine the outbound endpoint based on the content of properties in my custom XML message. Although this might look as common functionality I couldn’t find a complete example for this on the net. This one was close, but didn’t match completely with my situation: |
| 2 January |
Although there are a lot of evaluators available in Mule CE it is very easy to add your own evaluator. In my case we have a self defined message format that holds some properties in the header of a message (similar to JMS Message, MuleMessage, etc.). To get access to these properties in the Mule config I created a custom evaluator that made this possible. Although there will be other solutions available for this situation, I found this a nice (pragmatic) way to solve it. It also provides a base to start from in case of possible changes in the future. |
| 18 December |
In my current project we are going to need a BPEL engine besides our Mule CE implementation. Actually, we will use Mule for our stateless communication between systems and use BPEL for the stateful processes. One of the possible frameworks to use as a BPEL engine is Apache ODE. In this post I will show you how you can start a BPEL process in Apache ODE with Mule. As you will see, it is merely a combination of posts I made earlier, but I think it is nice to have the complete thing in one post. |
| 17 December |
Currently, I’m evaluating BPM/BPEL engines for a client. First up: Intalio|Server. Intalio|Server is based on Apache ODE and runs on Tomcat. Downloading and installing (read: unzipping) was easy. Starting it *seemed* easy. Just do Login using admin/changeit and notice the following: “Hmmm, Intalio claims the credentials are incorrect.” |
| 15 December |
Recently, Netbeans 6.8 GA was released. Great news … but unfortunately, SOA and UML support has disappeared from the release.
“Official” reaction from the Netbeans forum:
|
