Martin,
IOW -- a superset. Thanks. I'll go w/ AXIS.
Michael
"Martin Gainty"
<[EMAIL PROTECTED]
com> To
<[email protected]>
05/31/2005 10:00 cc
AM
Subject
Re: SOAP vs AXIS
Please respond to
[EMAIL PROTECTED]
he.org
Michael-
To quote the AXIS doc Axis
uses SAX which is an Event Based parser
It also support for multiple transports senders and listeners for SOAP over
various protocols such as SMTP, FTP, message-oriented middleware, etc
But Axis isn't just a SOAP engine -- it also includes:
a.. a simple stand-alone server,
b.. a server which plugs into servlet engines such as Tomcat,
c.. extensive support for the Web Service Description Language (WSDL),
d.. emitter tooling that generates Java classes from WSDL. (wsdl2java)
e.. some sample programs, and
f.. a tool for monitoring TCP/IP packets. (tcpmon)
check out
http://ws.apache.org/axis/java/user-guide.html
Martin-
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, May 31, 2005 11:22 AM
Subject: SOAP vs AXIS
>
>
>
>
> I'm starting to write an Java application that is invoked as a simple
> command-line app. The program will invoke a web service to retrieve some
> information. So far, I've been using AXIS for this, but as I read SOAP
> docs, it seems I could do the same w/ SOAP. I have also started to think
> (perhaps mistakenly) that AXIS is replacing SOAP.
>
> Is there a document that describes the pros/cons of SOAP vs AXIS? Should
> I
> continue w/ AXIS or should I be looking at SOAP?
>
> Thanks
> Michael Giroux
>
>
