You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Damien Boucquey <db...@eft.be> on 2001/04/26 10:40:21 UTC
SOAP Choice
Hi all,
Is SOAP a good choice for communication between a server and client when
both ones are developed by the same company, i.e. as a three tier
proprietary application, or is it an overkill ?
By the way, I tried the samples that came with Apache SOAP and got the
following message:
Fault: SOAP-ENV:Client, Unable to resolve URI namespace for "xsd"
Thanks,
D+
Note: This message and its attachements have been checked for viruses by InterScan VirusWall V3.4
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP Choice
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
graham glass wrote:
> i think that unless you're taking advantage of java-specific
> stuff like dynamic class loading, it is better to move towards
> a single-protocol environment, i.e. SOAP.
>
> when you move to a LAN, i bet that the efficiency differences
> between SOAP and RMI/JRMP would be insignificant, and the advantages
> are that every network service you build can be accessed
> from any platform/language.
it may heavily depend on your application though. if you are just exchanging
well defined short messages it may work perfectly but when performance is of
highest importance you should stick with RMI/JRMP or CORBA as they were
_designed_ to be efficient binary protocols.
> i view web services as being an improvement in how you go
> about architecting distributed systems, regardless of where
> they are deployed.
make them more robust and easier to deploy but in controlled environment
robustness may not be that hard to achieve but performance or low load on
resources may be important.
thanks,
alek
--
Aleksander Slominski, LH 316, IU, http://www.extreme.indiana.edu/~aslom
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall - Fujiwara no Teika(1162-1241)
Re: SOAP Choice
Posted by Amrit Jain <am...@netcontinuum.com>.
graham glass wrote:
> i think that unless you're taking advantage of java-specific
> stuff like dynamic class loading, it is better to move towards
> a single-protocol environment, i.e. SOAP.
>
> when you move to a LAN, i bet that the efficiency differences
> between SOAP and RMI/JRMP would be insignificant, and the advantages
> are that every network service you build can be accessed
> from any platform/language.
>
> i view web services as being an improvement in how you go
> about architecting distributed systems, regardless of where
> they are deployed.
>
> - graham
>
> -----Original Message-----
> From: Frederic Jeanne [mailto:fjeanne@symetrx.com]
> Sent: Thursday, April 26, 2001 5:49 AM
> To: soap-dev@xml.apache.org
> Subject: RE: SOAP Choice
>
> Hello Damien,
>
> SOAP for two applications running on the same LAN is only a good choice if
> one of both isn't a Java one (.NET for example). In the
> LAN communication paradigm between 2 java applications
> I would use an more efficient protocol like RMI/IIOP or JMS.
>
> To my opinion SOAP is suited for Internet application communications and
> inter legacy system communications.
>
> Anyway SOAP will work well on a LAN ;) !
> (If you plan a futur deployment on Internet begin with SOAP ...)
>
> FJ.
>
> -----Message d'origine-----
> De : Damien Boucquey [mailto:dboucquey@eft.be]
> Envoyé : jeudi 26 avril 2001 10:40
> À : SOAP-Dvp (E-mail); SOAP-User (E-mail)
> Objet : SOAP Choice
>
> Hi all,
>
> Is SOAP a good choice for communication between a server and client when
> both ones are developed by the same company, i.e. as a three tier
> proprietary application, or is it an overkill ?
>
> By the way, I tried the samples that came with Apache SOAP and got the
> following message:
> Fault: SOAP-ENV:Client, Unable to resolve URI namespace for "xsd"
>
> Thanks,
>
> D+
>
> Note: This message and its attachements have been checked for viruses by
> InterScan VirusWall V3.4
hey graham ...ur right...
RE: SOAP Choice
Posted by Frederic Jeanne <fj...@symetrx.com>.
Hello graham,
I share your vision and you are probably right for the
next generation of applications. But to be honnest SOAP
is a yound techno, so we can understand some hesitations of middleware
architects to only base their middleware on SOAP for an application which in
most case will be first deployed on a LAN and only used by the legacy
system.
Anyway, If a company provide all the RMI and JMS features and efficiencies
on a SOAP layer no doubt SOAP will be the best choice ;) !
I suppose RMI can be easily replaced by SOAP due to the RPC model used, but
to replace
the JMS features it will be an other affair.
The asynchonous communication paradigm seems not to interest the SOAP
community.
FJ.
-----Message d'origine-----
De : graham glass [mailto:graham-glass@mindspring.com]
Envoyé : jeudi 26 avril 2001 13:05
À : soap-dev@xml.apache.org
Objet : RE: SOAP Choice
i think that unless you're taking advantage of java-specific
stuff like dynamic class loading, it is better to move towards
a single-protocol environment, i.e. SOAP.
when you move to a LAN, i bet that the efficiency differences
between SOAP and RMI/JRMP would be insignificant, and the advantages
are that every network service you build can be accessed
from any platform/language.
i view web services as being an improvement in how you go
about architecting distributed systems, regardless of where
they are deployed.
- graham
-----Original Message-----
From: Frederic Jeanne [mailto:fjeanne@symetrx.com]
Sent: Thursday, April 26, 2001 5:49 AM
To: soap-dev@xml.apache.org
Subject: RE: SOAP Choice
Hello Damien,
SOAP for two applications running on the same LAN is only a good choice if
one of both isn't a Java one (.NET for example). In the
LAN communication paradigm between 2 java applications
I would use an more efficient protocol like RMI/IIOP or JMS.
To my opinion SOAP is suited for Internet application communications and
inter legacy system communications.
Anyway SOAP will work well on a LAN ;) !
(If you plan a futur deployment on Internet begin with SOAP ...)
FJ.
-----Message d'origine-----
De : Damien Boucquey [mailto:dboucquey@eft.be]
Envoyé : jeudi 26 avril 2001 10:40
À : SOAP-Dvp (E-mail); SOAP-User (E-mail)
Objet : SOAP Choice
Hi all,
Is SOAP a good choice for communication between a server and client when
both ones are developed by the same company, i.e. as a three tier
proprietary application, or is it an overkill ?
By the way, I tried the samples that came with Apache SOAP and got the
following message:
Fault: SOAP-ENV:Client, Unable to resolve URI namespace for "xsd"
Thanks,
D+
Note: This message and its attachements have been checked for viruses by
InterScan VirusWall V3.4
RE: SOAP Choice
Posted by graham glass <gr...@mindspring.com>.
i think that unless you're taking advantage of java-specific
stuff like dynamic class loading, it is better to move towards
a single-protocol environment, i.e. SOAP.
when you move to a LAN, i bet that the efficiency differences
between SOAP and RMI/JRMP would be insignificant, and the advantages
are that every network service you build can be accessed
from any platform/language.
i view web services as being an improvement in how you go
about architecting distributed systems, regardless of where
they are deployed.
- graham
-----Original Message-----
From: Frederic Jeanne [mailto:fjeanne@symetrx.com]
Sent: Thursday, April 26, 2001 5:49 AM
To: soap-dev@xml.apache.org
Subject: RE: SOAP Choice
Hello Damien,
SOAP for two applications running on the same LAN is only a good choice if
one of both isn't a Java one (.NET for example). In the
LAN communication paradigm between 2 java applications
I would use an more efficient protocol like RMI/IIOP or JMS.
To my opinion SOAP is suited for Internet application communications and
inter legacy system communications.
Anyway SOAP will work well on a LAN ;) !
(If you plan a futur deployment on Internet begin with SOAP ...)
FJ.
-----Message d'origine-----
De : Damien Boucquey [mailto:dboucquey@eft.be]
Envoyé : jeudi 26 avril 2001 10:40
À : SOAP-Dvp (E-mail); SOAP-User (E-mail)
Objet : SOAP Choice
Hi all,
Is SOAP a good choice for communication between a server and client when
both ones are developed by the same company, i.e. as a three tier
proprietary application, or is it an overkill ?
By the way, I tried the samples that came with Apache SOAP and got the
following message:
Fault: SOAP-ENV:Client, Unable to resolve URI namespace for "xsd"
Thanks,
D+
Note: This message and its attachements have been checked for viruses by
InterScan VirusWall V3.4
RE: SOAP Choice
Posted by Frederic Jeanne <fj...@symetrx.com>.
Hello Damien,
SOAP for two applications running on the same LAN is only a good choice if
one of both isn't a Java one (.NET for example). In the
LAN communication paradigm between 2 java applications
I would use an more efficient protocol like RMI/IIOP or JMS.
To my opinion SOAP is suited for Internet application communications and
inter legacy system communications.
Anyway SOAP will work well on a LAN ;) !
(If you plan a futur deployment on Internet begin with SOAP ...)
FJ.
-----Message d'origine-----
De : Damien Boucquey [mailto:dboucquey@eft.be]
Envoyé : jeudi 26 avril 2001 10:40
À : SOAP-Dvp (E-mail); SOAP-User (E-mail)
Objet : SOAP Choice
Hi all,
Is SOAP a good choice for communication between a server and client when
both ones are developed by the same company, i.e. as a three tier
proprietary application, or is it an overkill ?
By the way, I tried the samples that came with Apache SOAP and got the
following message:
Fault: SOAP-ENV:Client, Unable to resolve URI namespace for "xsd"
Thanks,
D+
Note: This message and its attachements have been checked for viruses by
InterScan VirusWall V3.4