I've gone 'half way' - I've created a service that tracks and publishes Jini services as web services - either as SOAP using JAX-WS, or as a RESTful resource using JAX-RS (or both at that same time). I did this using an embedded Grizzly HTTP container, and it's all built in Dennis Reedy's Rio framework.
As both of these technologies are annotations-driven, I had quite a tough time with this. The "thing" to ultimately expose as a service ends up being a generated smart proxy (i.e. a Rio proxy), and this has lost all the annotations. I had to use BCEL to generate, on the fly, a new proxy on top of this smart proxy, one which has the annotations from the original service interface applied to it, so that standard frameworks can expose it as a valid web service. This generated proxy also needed to properly track the service disappearing and re-appearing, so that it can publish/unpublish the service. I imagine it won't be extremely different to expose a service as a web socket channel - one would just have to figure out what you want this channel to map to, i.e. requests/responses from some Jini service, or Jini events, or whatever. I have not been in a position to open-source my Jini web container just yet (even though I wrote it almost two years ago, gulp!). When I am in a position to do so, I'll definitely share it on this list. Good luck! In the world of today, Jini really needs seemless web interoperability - both to consume and expose services. Dawid Loubser On 28/05/2014 07:51, Bishnu Gautam wrote: > Hi all > Have anyone tried to integrate river application with WebSocket Application. > If anyone have experience, could you share it. That would be a great help. > RegardsBishnu >
signature.asc
Description: OpenPGP digital signature
