With the release of Mule ESB 2.2.7 (and the upcoming 3.1.0), you will see a reloaded version of the PGP module. The previous version was using the Cryptix library which currently RIP and doesn’t handle large files.
The new version uses the bouncy castle library which allows handling encryption and decryption using streams. We have added some integration tests that were necessary to update the library and the code safely.
Mule configuration files are Spring XML files by nature. So the XML editor is an important development tool and provides a lot of benefit. When working in Eclipse, it provides:
The Mule team is pleased to announce the availability of the first release candidate for Mule ESB 3.1. This is a continuing evolution of the Mule 3 architecture, first introduced in Mule 3.0 , and follows hot on the heels of our most recent release, Mule ESB 3.0.1.
The biggest enhancements in Mule 3.1 are the new features for Mule Cloud Connect. It is now very simple to,
This release includes several important improvements to Mule ESB that were developed in close collaboration with our customers:
The Mule project just had its 8th anniversary. I find anniversaries a great time to reflect and set new goals. Mule has come along way from the days when I was coding on the couch while my housemate and girlfriend watched Big Brother (I never got reality TV). I started Mule out of pure frustration born from having to perform the same integration tasks for every new project I worked on and the fact that middleware seemed to be a big vendor sport with very poor tools for actually building integration solutions.
Recently I saw this question posted in a forum: “Does REST have better performance than SOAP”?
This question is symptomatic of a fundamental misunderstanding of REST, I think. SOAP is a particular protocol used to implement RPC functionality. REST, on the other hand, is not a technology or protocol, but an architectural style. Systems that were built with the REST architectural style are fundamentally different from RPC based systems. For REST, we think in resources and data.
One of the joys of Mule 3’s new Message Processor (MP for short) architecture is the power that arises from being able to combine message processors into different patterns. To make this as flexible as possible, the routing message processors that were designed to be used in flows each do a single job, making them highly reusable. This allows you to build up a flow piece by piece, or alternatively modify an already working flow,
A couple of weeks ago I started the integration between Mule ESB and Activiti BPMN. Activiti is a Business Process Management (BPM) and workflow system targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It’s open-source and distributed under the Apache license. Activiti is being written from the ground up with the requirement that the engine should be easily embedded and that the project would be aimed at developers not the business.