Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Subject: Re: Exporters for other RPC frameworks
To: <dev@river.apache.org>
References: <beb6957b0d836517840fe924904961d5@org.tizen.email>
 <CAK_o9cG4ND7-vBNP4_+eq_oW9msuHBAK01wdvrJXP8TKjz3fzA@mail.gmail.com>
From: Dawid Loubser <dawid@travellinck.com>
Message-ID: <cd2514d8-3e01-bf4d-91bc-20a21524460b@travellinck.com>
Date: Tue, 6 Sep 2016 14:48:51 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <CAK_o9cG4ND7-vBNP4_+eq_oW9msuHBAK01wdvrJXP8TKjz3fzA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 06 Sep 2016 12:49:24 -0000

I'm going to have a chat to the client (I don't do that much work for
them anymore).
And I will have to dust off what I did, and probably generalise it - it
was for very specific circumstances, developed in a hurry, but it's been
running on a couple of services in production for 4 years, so the basics
hold up :-)

To be honest, I haven't looked at the work you guys have been doing on
River 3 - but that would be a good starting point.

What I did, was basically to write a service (which wraps a web
container), which you could configure to look for other services
(usually by type, but perhaps using other service properties as
selection criteria). It would generate "smart" proxies (which track, and
delegate calls to, a normal Jini service) and expose them as your choice
of web service style (SOAP, REST) and manage them in the embedded web
container.

chat soon -
Dawid


On 06/09/2016 13:32, Bryan Thompson wrote:
> +1  I see exposing Jini / River more broadly as key.
>
> Bryan
>
> On Tue, Sep 6, 2016 at 4:18 AM, Peter <jini@zeus.net.au> wrote:
>
>> 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 audie=
nce
>> 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 <dawid@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 belie=
ve
>> - 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.
>>>
>>>
>>
>>
>>