Until recently, the XMPP transport was developed on its own feature branch to make sure it doesn’t interfere with the regular Mule 3 development.
I’ve been blogging recently about the usefulness of the transport. That blog post included a link to a custom bamboo build plan from which you could download a Mule distribution that included the new XMPP transport. Dowloading a full Mule release just to try out a new transport seems overly complex.
I’m pleased to announce that Mule team has just released 3.0 Milestone 2. Before we get into the features coming in Mule 3.0, I’d like to talk about the theme for this release. The overall theme for Mule 3.0 is simplicity. We are looking at every part of Mule to see what we can do to make things even easier. Mule is a powerful platform, but we realise not everyone wants or needs all that power.
At TSSJS last week I had a conversation with a Mule user that was having a problem invoking more than one method on a service component (just a POJO object). His scenario was that he had a service with multiple inbound endpoints and a service component with multiple methods, some with matching parameter types. Existing Mule users will be aware that Mule will match methods against the parameters received in the current message. Thus is two methods have the same parameters Mule cannot match the method to invoke.
We’re pleased to announce the immediate availability of our newest release of Tcat Server 6. This new release includes many fixes, in addition to bundling the Apache Software Foundation’s official release binaries of the newest Tomcat release, version 6.0.26.
Here is a summary of the changes and fixes that are included in the new version of Tomcat, since our last release of Tcat Server 6:
I had a great time at Qcon London last week, it really is one of the more forward thinking conferences out there for the enterprise. I gave two talks on ESBs and Enterprise Mashups so I figured I’d share the slides.
One of the good things about Apache Tomcat is that it is world’s most efficient and effective application server for running web applications. Legacy Java EE application servers can be more trouble than they are worth due to their inherent complexity and feature bloat.
In January of this year, the Apache Software Foundation released, Tomcat 6.0.24 , which made major improvements in finding and preventing memory leaks in web applications.
It has been a while since I last blogged about the new XMPP transport for Mule ESB. I’ve been making slow progress since then, but I’ve finally arrived at a point where the transport is starting to be useable. I’d like to show that by building a simple jabber client using the XMPP and stdio transports.
The Lean Startups movement has produced several important and successful techniques that can yield benefits to all types of organizations. One of these is continuous deployment — a process in which all code written for an application is immediately deployed into production. The result is a dramatic reduction in the development cycle time and the freeing of individual initiative. You can read about it here as described by Eric Ries.
In a recent post by Loraine Lawson on ITBusinessEdge, an informal survey was cited that referenced a majority of mid-market CIOs who “said they had no current business need for SOA.” I was a little surprised by the headline since MuleSoft continues to see tremendous adoption of our open source Mule ESB and subscriptions of our enterprise version among companies I would describe as mid-market. So, I decided to read further and try to learn more.
Mule community member, author, and consultant Eugene Ciurana recently discussed a technique for extending or modifying the run-time code in Mule without stopping the server, greatly reducing development time for Mule apps.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.