First release including the new XMPP transport

motif

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. So I decided to replace the existing XMPP transport with the new one in the Mule 3.0.0-M2 release we recently published.

So if you want to play with the new XMPP transport, download the Mule 3.0.0-M2 release and have fun.

As always, I’d like to hear from you if the new transport is useful or if you find any bugs with it.


We'd love to hear your opinion on this post


4 Responses to “First release including the new XMPP transport”

  1. Dirk, will your XMPP transport be capable of using BOSH (http://xmpp.org/extensions/xep-0206.html)?

  2. The XMPP transport currently uses the SMACK API so it can do everything that this API allows us. A quick google search on this shows that it currently doesn’t (see http://www.igniterealtime.org/issues/browse/SMACK-187).

  3. Hi Dirk!
    I would like to use the XMPP transport to receive packets regardless of who sent it and which type it is.

    Is this possible?

  4. Kalle, this is currently not implemented. But I think it’s possible to create an XmppAnyConversation and modify the namespace handler to allow it … doable but a bit of work.