Thanks Dawid, talk about surpassing expectations. That's great news if you're able to donate your webservices works to River, I agree, it will expose River to a potentially much wider audience with needs that River is presently unable to cater for, and may ignite greater interest as a result.
Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Dawid Loubser <da...@travellinck.com> Sent: 06/09/2016 07:37:26 pm To: dev@river.apache.org Subject: Re: Exporters for other RPC frameworks In 2012, I wrote infrastructure to export Jini services (running in Dennis Reedy's Rio service provisioning infrastructure) as either SOAP/XML web services, or RESTful JSON services, or - uniquely I believe - both at the same time without having to write adaptors or different interfaces. I remember having to write some tricky smart-proxy generation code (I used ASM at the time) in order to end up with proxies which JAX-WS and JAX-RS would be happy to expose (in an embedded Grizzly web container) - and dealing smoothly with services coming, going, and moving. If anybody would be interested in my work in this space - even though I did it commercially, I believe the client will be open to me open-sourcing it. But basically, I think there is a strong need to expose Jini services "at the edges" to common protocols like SOAP or RESTful JSON/HTTP. I couldn't find anything, which is why I wrote my own. warm regards, Dawid Loubser On 06/09/2016 11:12, Peter Firmstone wrote: > Anyone interested in Exporters for other RPC Frameworks? > > If so which and why? > > Pete. > > Sent from my Samsung device. > >
