|
From: Seth L. <set...@gm...> - 2005-03-10 18:18:58
|
On Thu, 10 Mar 2005 09:00:17 +0100, Steven Devijver <ste...@gm...> wrote: > Just for my understanding, are you talking about Jini integration for > Spring or remoting for Spring? > > Currently there is no remoting support for JMS since - like Jini - > this is an asynchronous service. Calling a remote method and receiving > a result or exception asynchronously for me lies somewhere between > undoable and very difficult. Two things: Jini is not asynchronous by nature. In fact, it's neither. Jini supports remote Events (asynchronous) and regular RPC synchronous semantics. It depends on how you implement your service. Jini's standard remote proxies work almost identically like standard RMI proxies. So it's a nature fit with Spring's existing remoting support, and remote client support. Also, check out the JMS sandbox. There is some code in there to treat JMS just like a Spring remote exportable service. I haven't played with the code yet, but it sounds like what you're looking for. I actually think Jini integration would be a great addition for Spring. Spring hides all the complexity of exporting services, and consuming services. Spring uses interfaces a lot, and so does Jini. Spring's ApplicationContext has Events, and so does Jini. If I can remove yet another config line and use Jini's automated lookup and service registration, all the better! :) Seth -- <a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a> <a href="http://www.foaf-project.org/">What is FOAF?</a> |