Salut,
(you probably saw my answer in Atmosphere, but if Jersey folks are
interested)
You can write your own WebSocket sub protocol in Atmosphere, as
described here
http://groups.google.com/group/atmosphere-framework/msg/26680ea5fbef130b
A+
-- Jeanfrancois
On 12-02-28 1:33 PM, Jeremy Johnson wrote:
>
> ***NOTE: The subscribe/unsubscribe page for the Jersey mailing list is
> broken so I can't properly subscribe. Please be so kind as to forward
> any responses to jeremy_at_imtc.gatech.edu
> <mailto:jeremy_at_imtc.gatech.edu>. Thanks! ***
>
> I'm building a server that exposes both a RESTful web service via
> Jersey as well as a WebSocket interface with a custom subprotocol. In
> addition to its other duties, I'd like for my WebSocket server to be
> able to perform CRUD operations on my Jersey resources.
>
> I know that the Atmosphere framework supports Jersey integration,
> however I need to use my own WebSocket subprotocol.
>
> Can anyone provide a few pointers on how I might glue Jersey to my
> WebSocket server? (They're both running in the same embedded Jetty
> process.) Do I need to just use Java reflection to process the Jersey
> attributes or does Jersey offer any higher level abstraction that I
> could make use of?
>
> Thanks!
>
> Jeremy
>