Here at Mulesoft, we use Jira for a lot of different things: tracking hiring, IT tasks, reporting product bugs, planning releases, etc.
We recently upgraded our Jira instances to the latest 4.2 version. One of my favorite new features is the ability to create your own search query in a SQL-like syntax. This allows you to customize your searches in all new ways. For example,
We’re very happy to announce Tcat 6 R4.3. This latest release of Tcat Server builds on Tcat 6 R4, making life even easier for Tomcat users. Enhancements in this release include:
- Solaris support: Driven by customer demand, Tcat Server now includes a Solaris installer and deeply integrates with the Solaris 10 Service Management Framework (SMF), supporting standard service querying, stops, starts, and restarts.
Mule 3.1 introduces a very useful new <logger> element that makes it easy to inspect the content and properties of your messages in Mule while building or debugging a flow. It’s also perfect for logging errors, info messages etc. Mule has always supported logging with the <log-component> but while working with the new orchestration capabilities of Mule 3 flows, we found a real need for fine-grained logging. With the new message processor architecture,
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:
- Schema documentation assistance for the element you are configuring
- Validation of your schema and context of any errors that are detected
- Autocomplete of elements and attributes based on what is valid in the current element of configuration you are editing
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,
I’m happy to announce the release of Mule ESB 2.2.7 Enterprise. This release represents the most stable version of Mule ESB, with over 400 bug fixes since Mule ESB 2.2.1 Community.
This release includes several important improvements to Mule ESB that were developed in close collaboration with our customers:
- The JDBC transport in Mule is now more flexible and enhanced with additional native support for database platform-specific features (for more info).
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.
In order to use the hot deployment feature that was introduced with Mule 3 you need to package your application as a zip file.
If you are using Maven to build your Mule applications then packaging zip files for hot deployment is very easy. All you need is to declare your packaging to be Mule: