I wondered if anyone has built an async interface to REST without JMS as in JAX-WS.

Thanks,
John Harby

I know this is a little old, but Im really intrerested in this approach to ubiquitous access to a messaging system.

I believe the need is there for a greater decoupling of messaging clients from the servers implementation. Projects I have seen recently have run into severe difficulties talking to messaging systems from disparate JMS providers, due to the clients needing to very carefully manage the messaging client libraries for each provider concurrently. Without an OSGi system, this can get really tricky indeed.

REST as an architectural style seems to bring a lot to the table when trying to solve this problem, particularly providing a standard coms protocol, if we assume HTTP.

My main concern or challenge I see with providing a RESTful interface to a messaging system (JMS for example) would be allowing for XA interactions with the messaging provider. Of course this more of a WS problem generally. Is this something you have considered?

Cheers,
Ross

the standard HTTP 1.1 definition of PUT tells the user of our messaging system that sending a message is idempotent and they don’t have to worry about performing resends

Strictly speaking this is untrue. RFC-2616 (HTTP/1.1) explicitly states that “HTTP/1.1 does not define how a PUT method affects the state of an origin server.”

We are a current JBOSS customer and am planning to use RESTEasy in a pending project. All in all looks like a great framework. One question. We will be developing an interface for distributing near realtime call event/presence data to web clients. Are there plans to extend the RESTEasy framework to support COMET interactions?

Regards,

Mike

Enjoyed the NEJUG talk! Have you checked this out yet?

http://www.lunatech-research.com/archives/2008/03/20/restful-web-sevices-resteasy-jax-rs

Regards,

Todd