----- Original Message -----
From: "Sam Wun" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Wednesday, April 09, 2008 4:21 PM
Subject: Why use SOAP in Java
Hi,
I am wondering why use SOAP with Java?
Since SOAP is based on RPC, I think the best question may be asked, why
use RPC for client-server application?
Web Browser ---(HTTP) --- Tomcat Servlet/JSP
Java/C/VB/.Net Application -----(Soap) ---- Tomcat Server (Axis)
Java Application ------- (RMI) ------- Application Server (Beans)
Browser Served Applications -----(HTTP)------ Tomcat Harbor (Applications)
Its all related - protocols ontop of protocols, ie SOAP is an XML format
ontop of HTTP
And there is a lot of overlap, a programmer may decide to use a HTTP client
and call (POST or GET) for a simple value from a Tomcat, whereas SOAP would
translate parameters for you.
Probably the most general technology out there is browser against web
server, but sometimes the others are more useful... for example a remote
.Net programmer wants to call a function (web service) (soap) that you have
written in java on (axis) tomcat (in theory anyway).
But you need to study all these technologies because there is no perfect
solution.
Soap is quite slow, Ejb is hard to learn and servers are all different, but
well supported, Harbor is made by a crazy guy that loves Tomcat and doesnt
want to use anything else;)
If you can use a servlet (Tomcat) against a browser.... always a good
solution that one wants to move away from reluctantly... my feeling anyway.
Have fun...
Thanks
---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
