endpoints into XML using something like JAXB.
>
>
> francis
>
>
>
>
> >> -Original Message-
> >> From: soap beginner
> [mailto:[EMAIL PROTECTED]]
> >> Sent: Sunday, September 30, 2001 7:10 AM
> >> To: [EMAIL PROTECTED]
> >>
gt; To: [EMAIL PROTECTED]
>> Subject: RE: SOAP over RMI, Pointless?
>>
>>
>> I am still slightly confused.
>> The number one factor is the data to be exchanged is
>> XML.
>> Yes servers are written in Java.
>> We have a client side interface to RMI, J-Integra
check out: http://www.extreme.indiana.edu/soap/
-Original Message-
From: soap beginner [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 30, 2001 6:10 AM
To: [EMAIL PROTECTED]
Subject: RE: SOAP over RMI, Pointless?
I am still slightly confused.
The number one factor is the data to be
XB) into XML for VB
> consumption. To talk to
> COM, you can try a number of COM bridges.
>
> I hope this helps,
>
>
> francis
>
>
>
>
> >> -Original Message-
> >> From: soap beginner
> [mailto:[EMAIL PROTECTED]]
> >> Sent
XB) into XML for VB
> consumption. To talk to
> COM, you can try a number of COM bridges.
>
> I hope this helps,
>
>
> francis
>
>
>
>
> >> -Original Message-
> >> From: soap beginner
> [mailto:[EMAIL PROTECTED]]
> >> Sent
try GLUE: http://www.themindelectric.com
cheers,
graham
-Original Message-
From: soap beginner [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 29, 2001 4:45 AM
To: [EMAIL PROTECTED]
Subject: Re: SOAP over RMI, Pointless?
No we hava a VB Client, but s strict requirment to
helps,
francis
>> -Original Message-
>> From: soap beginner [mailto:[EMAIL PROTECTED]]
>> Sent: Saturday, September 29, 2001 5:45 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: SOAP over RMI, Pointless?
>>
>>
>> No we hava a VB Client, bu
No we hava a VB Client, but s strict requirment to
communicate using XML. We cannot use HTTP. We may add
more clients eventually, or be able to use HTTP. Why
write something to interpret XML to call services when
its already been done?
The client will be taking to use using COM or RMI.
I don't se
let me get this straight... you're going to have a Java client, and a Java
server, and do the communication over RMI, but have the method invocation
done using SOAP? By the sounds of things you realise this isn't exactly,
ahem, ideal,... but are having trouble convincing a client?
IMHO:
RMI:
