Return-Path: Mailing-List: contact soap-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-user@xml.apache.org Received: (qmail 47513 invoked from network); 14 Jun 2002 07:18:19 -0000 Received: from unknown (HELO www.mizarworks.com) (217.130.26.66) by daedalus.apache.org with SMTP; 14 Jun 2002 07:18:19 -0000 Received: from carlos ([213.9.248.3]) by www.mizarworks.com (8.11.0/8.11.0) with SMTP id g5E791o26502 for ; Fri, 14 Jun 2002 09:09:02 +0200 Message-ID: <032601c21373$8bbe0c50$5207a8c0@carlos> From: "Carlos Lozano Ruiz" To: References: <00d401c212f6$2476b790$a0b2f781@kn.op.dlr.de> Subject: Re: Provider for Jini-Services Date: Fri, 14 Jun 2002 09:17:29 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0323_01C21384.4ED751A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0323_01C21384.4ED751A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I am currently working on project that involves both technologies = (JINI and SOAP) but I am using the following approach: ClientSOAP----------(1-request)-------->ServerSOAP&ClientJini----------(2= -request)--------->ServerJini ClientSOAP<-------(4-response)------- = ServerSOAP&ClientJini<--------(3-response)------- ServerJini So I have had to develope a class that acts as a ServerSOAP but in = fact is just a Jini client and the real server that provides all the = logic is a Jini Server. This is the simplest way I have found to join = SOAP and JINI but I think the idea of building a "RPCJiniProvider" as = you suggest should be the right way to use these two technologies. =20 ----- Original Message -----=20 From: Christian Bock=20 To: soap-user@xml.apache.org=20 Sent: Thursday, June 13, 2002 6:19 PM Subject: Provider for Jini-Services Hi to all! Currently I am working on my deploma-thesis with the task to use Jini-Services from small mobile devices (CLDC/MIDP) What I've done so far is to start an implementation of a bridge=20 between Apache-XML-RPC and kXML-RPC ( from Enhydra ) but now I want to use Apache-SOAP and kSOAP because it has the big advantage of the ClassMappingRegistry. So my question is if someone out there already had the same idea of bridging JINI and SOAP and is or was working on a "RPCJiniProvider" ? comments are welcome! chris ------=_NextPart_000_0323_01C21384.4ED751A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
   I am currently working on = project that=20 involves both technologies (JINI and SOAP) but I am using the following=20 approach:
 
ClientSOAP----------(1-request)-------->ServerSOAP&Client= Jini----------(2-request)--------->ServerJini
ClientSOAP<-------(4-response)-------=20 ServerSOAP&ClientJini<--------(3-response)------- =20 ServerJini
 
   So I have had to develope = a class that=20 acts as a ServerSOAP but in fact is just a Jini client and the real = server that=20 provides all the logic is a Jini Server. This is the simplest way I have = found=20 to join SOAP and JINI but I think the idea of building a = "RPCJiniProvider"=20 as you suggest should be the right way to use these two=20 technologies.
 
 
----- Original Message -----
From:=20 Christian Bock
Sent: Thursday, June 13, 2002 = 6:19=20 PM
Subject: Provider for = Jini-Services

Hi to all!
 
Currently I am working on my = deploma-thesis with=20 the task
to use Jini-Services from small = mobile devices=20 (CLDC/MIDP)
What I've done so far is to = start an=20 implementation of a bridge
between Apache-XML-RPC and kXML-RPC ( = from=20 Enhydra )
but now I want to use Apache-SOAP and = kSOAP=20 because
it has the big advantage of the=20 ClassMappingRegistry.
So my question is if someone out = there already=20 had the same
idea of bridging JINI and SOAP = and=20 is or was working on a
"RPCJiniProvider" ?
 
comments are welcome!
 
chris
 
 
 
------=_NextPart_000_0323_01C21384.4ED751A0--