About
Disclaimer: the views expressed on this site are mine alone and do not necessarily reflect the views of my employer or its affiliated entities.
Integration
It looks like the word is spreading that the FUSE has a new release out. The release includes enhancements across the FUSE family of products including, FUSE ESB, FUSE Message Broker, FUSE Services Framework and FUSE Mediation Router. The releases include significant performance and feature improvements and tighter integration between the FUSE ESB and all components of the product family.
For those of you who don’t know, the FUSE family of products are IONA supported versions of several Apache projects like ActiveMQ and ServiceMix.
Congratulations to the ServiceMix project for graduating from the Incubator! Having participated in several projects that have graduated from the Apache incubator, I can attest that this is an awesome milestone to have completed.
For those of you who don’t know what ServiceMix is, it’s by far the BEST open source ESB available today. The components in this ESB use the JBI 1.0 spec to integrate so end users and component developers can avoid the vendor lock in that is so common in todays commercial ESB space.
I’m one of those guys that thinks that REST is great technology. Sure, REST is does not do everything that SOAP can do, but I think that REST is built to be SIMPLE, something that SOAP and it’s WS-* buddies forgot about.
What we are missing is a good standard way to map REST to the simple POJO programming model that most of the Java industry has been quickly adopting. Seems SeXFire Dan has good start on a way of doing that!
Dan if you read this, I would make it even simpler if by default the method names for a service are determined by convention. For example, for a given XService, the methods:
deleteX(…): is automatically mapped to a HttpMethod.DELETE
addX(…): is automatically mapped to HttpMethod.POST
updateX(…): is automatically mapped to a HttpMethod.PUT