netzooid

This is a little late, but it seems that MuleSource has been declared a Cool Vendor in SOA Governance by Gartner for our Galaxy product.

Eat that all you people in middle school who told me I’d never be cool.

In related news – while they don’t call me cool, Search SOA has a two part interview with me on Galaxy/REST/UDDI and other subjects.

Seems there has been some more work on Atom over XMPP recently:

There’s been plenty of talk recently about using XMPP to build a decentralized microblogging platform (think Twitter busted apart to run as a distributed network of microblogging providers). Indeed, as Bob Wyman points out, we have all the pieces:

• The core XMPP infrastructure, comprised of 100,000+ messaging and presence servers plus millions of end users.
• The XMPP publish-subscribe extension, specifically the personal eventing profile thereof, which enables your IM account to function as a virtual pubsub service and thus push out all sorts of notifications about you.
• The Atom syndication format along with the Atom threading extension, which (being XML) is easily transported over XMPP.

Now it’s just a matter of putting the pieces together, so Joe Hildebrand and I have done just that in a little spec we call Microblogging Over XMPP. Feedback is welcome!

This builds on the Atomsub spec that Peter Sainte-Andrew (and others?) have been working on. Cool stuff.

Note to self: create a UDDI replication replacement based on Atom and XMPP.

Let the new appserver war begin.

Is there any standard way to package up applications for OSGi? Spring has PARs now. Equinox seems to have their way. There is also P2 for remote access.

I don’t confess to be an OSGi expert, but I’m wondering – does it make sense to find a way to package applications up for OSGi appservers in a standard fashion? Or is it really something that needs to be server specific?

I’ve recently started using the Maven Eclipse plugin that was started by Sonatype and I have to say -wow, this rocks.

I went to start a Maven plugin today. Normally I would’ve googled around until I found an example. Then I would copied that example and started tweaking it.

With m2eclipse it was dead easy to just do New->Maven Project, then select the Maven plugin archetype.

Next I needed to add a dependency. Previously I would’ve searched around the maven repo manually or use mvnrepository.com. Now I just do right click->Maven->Add Dependency. Then I can type in something, like say “groovy” and it will present me all the versions that match. Its great.

Next I needed to test my plugin. Normally I would have to intsall the plugin then test it from another project. The m2eclipse plugin allows me to test the plugin “in-situ”. I don’t have to go through the time consuming phase of installing the plugin first anymore!

There’s a whole host of other features too:

• I can run maven builds from the IDE with a simple keystroke/click of the mouse
• It synthesizes projects from your source control. No mvn eclipse:eclipse needed any more. It also works much much better than the command line eclipse plugin.
• Easily add plugins to POMs

This is really going to help bring Maven to the masses. My only gripe is their ugly red icon

Update: fixed the mvnrepository.com url.