jms
I’m pleased to announce the release of RMI via JMS 1.0! RMI via JMS allows you do RMI style remoting over any JMS provider. It combines the ease of RMI development with flexibility and loose coupling that JMS provides.
It also supports and even simpler interface remoting model which does not mandate the throwing of RemoteException or extending the RemoteObject interfaces. It even allows remoting classes which don’t implement any interfaces via ASM magic.
Documentation still needs a little work, but the project is now ASL 2.0 Licensed and looking for contributions! Please join the mailing lists to get involved.
OMG, James is at it again! He whipped up the new StompConnect project at a blink of an eye. Firstly, let me introduce you to Stomp. Stomp was designed to be a super simple wire protocol for clients to talk to Message Oriented Middleware (MOM), like ActiveMQ. Since the protocol is text based and simple to implement, multiple language clients and servers were created with little effort.
And now thanks StompConnect, every JMS compliant MOM in existence (which is like almost all of them) can now be talked to using Stomp! This is a huge deal since the wire protocol for most JMS servers is proprietary and and getting a pure language client for any given mom was either difficult or impossible!