On Sep 22, 2010, at 1:48 AM, Jason Dillon <[email protected]> wrote:
> On Sep 21, 2010, at 7:54 PM, [email protected] wrote:
>> On Sep 21, 2010, at 6:28 PM, Jason Dillon <[email protected]> wrote:
>>
>>> Just wondering if you guys know of anyone doing JAX-RS over JMS?
>>
>> Yea. The CXF JAXRS implementation can do this. We have several systems
>> tests testing this.
>
> Yes I saw that later when I did some more research. Was it hard to do?
Not for CXF, no. But that's because the CXF JAXRS impl is built on the CXF core
which has a good transport API and already had a JMS transport. Pretty much any
transport written for CXF can be used for both the SOAP and REST sides of
things with very little effort. One thing that's consistently on my todo list
(never have the time) is to try using the Camel transport for CXF and try a
bunch of the Camel adapters to do JAXRS over all kinds of transports. It works
well for SOAP, just have had time to try for the REST things.
> Would it be hard to get Wink to do this too?
No idea. Never cared enough about Wink to look into things at that level.
Dan
>
> --jason
>
>
>> Dan
>>
>>
>>> Specifically, using JMS to establish the communication channel, then
>>> send/rx REST messages ver that channel (instead of making a new HTTP
>>> request each time). ATM my main users are a java client, though need to
>>> keep the window open for a web UI later and I'd like to keep using JAX-RS
>>> bits as the main entry point. Just that I would rather connect/secure the
>>> clients channel once and then overload it for passing async messages back
>>> via cometd-ishly as well. That and HTTP is pissing me off.
>>>
>>> Anyways, anyone know if this exists somewhere and if not how difficult it
>>> might be to implement a JMS transport for wink?
>>>
>>> --jason
>>
>
