RE: Apache SOAP vs AXIS

[dumdum 420]

Thanx anne for the reply. I have another question that my axis client is going to be Visual Basic application ,I beleive my webservice is based on RPC/ecoding , so this means I have to rewrite it with Document/Literal and if so how difficult is the change. Any pointers will help a lot.

Bhanu Pabreja.


From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: Apache SOAP vs AXIS
Date: Tue, 21 Jan 2003 19:38:55 -0500

SOAP supports two ways to construct a message: either as a Document or as an
RPC. You specify the construction method in the WSDL binding description
with the style= attribute (style="document" or style="rpc"). SOAP also
supports two ways to encode the message: either using an XML Schema or using
the SOAP encoding data model. You specify the enocding style in the WSDL
binding description with the use= attribute (use="literal" or
use="encoded"). Normally you use Document with literal and RPC with encoded.
(I've never seen anyone use document/encoded, although you might see someone
use rpc/literal -- very few implementations support rpc/literal, though).

Microsoft has always supported document/literal by default. If you want to
interoperate with MS SOAP Toolkit or .NET, you need to use doc/literal.

Anne

> -----Original Message-----
> From: dumdum 420 [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 21, 2003 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Apache SOAP vs AXIS
>
>
> axis supports not only RPC/encoded but also doc/literal can this
> be further
> explained.
>
> dumdum
>
> From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: <[EMAIL PROTECTED]>
> Subject: RE: Apache SOAP vs AXIS
> Date: Fri, 17 Jan 2003 13:29:32 -0500
>
> The Java community process has defined standard Java APIs for
> SOAP (JAX-RPC,
> JAXM, and SAAJ). Axis supports JAX-RPC and SAAJ. Quite a few other SOAP
> implementations now use these APIs. Apache SOAP predates these
> APIs. It has
> a proprietary API that only works with Apache SOAP. (JAX-RPC is to SOAP as
> JDBC is to databases)
>
> Axis is designed as a flexible, modular, extensible runtime system. It's
> very easy to add middleware functionality to the SOAP message processing
> system. And you don't need access to the source code to do so.
> For example,
> you can add handlers to do things like auditing, logging, authentication,
> authorization, message correlation, transaction control, reliability, etc.
> Apache SOAP doesn't give you this kind of capability. You often
> need access
> to the source code to add new capabilities. And you really don't want to
> mess too much with the source code. It's not flexible and modular. Axis
> provides a specific type of handler that makes it really easy for you to
> create and process SOAP Headers. Apache SOAP does not.
>
> Anne
>
> > -----Original Message-----
> > From: dumdum 420 [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, January 17, 2003 11:16 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Apache SOAP vs AXIS
> >
> >
> > Well but why would Apache SOAP API be proprietary since it is an open
> > sources?
> >
> > Also can u explain the headers in little detail just to be more
> > clear on the
> > topic.
> >
> > Why would even Apache SOAP have extensibility issues.
> >
> > Well ... though it looks that AXIS is the clear winner.
> >
> > Thanx in advance.
> >
> > Bhanu
> >
> >
> >
> >
> >
> > From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: <[EMAIL PROTECTED]>
> > Subject: RE: Apache SOAP vs AXIS
> > Date: Thu, 16 Jan 2003 16:51:40 -0500
> >
> > I hate to break it to you, but Microsoft .NET and Microsoft SOAP
> > Toolkit are
> > the two most common systems used to access SOAP.
> >
> > I agree that Axis is the most commonly used SOAP implementation
> > for Java. I
> > don't think Apache SOAP fits in that category anymore, though.
> > Use of Apache
> > SOAP has definitely dropped off since Axis was released. Other
> > very popular
> > Java SOAP implementations include IBM WSTK (based on Axis), Systinet
> WASP,
> > The Mind Electric GLUE, and IONA XMLBus. I suspect that BEA,
> > Borland (based
> > on Axis), Oracle, and Marcomedia (based on Axis) have a pretty
> significant
> > share also.
> >
> > Here's a quick comparison between Apache SOAP and Axis:
> >
> > SOAP Axis
> > ---- ----
> > really old third generation
> > really slow much faster, but not as fast as many
> > no WSDL support WSDL support
> > proprietary API JAX-RPC API
> > RPC/encoded only RPC/encoded and Doc/literal
> > interoperability issues very interoperable
> > extensiblity issues very extensible
> > low level API for headers easy handler support for headers
> >
> > In other words, don't even consider using SOAP.
> >
> > Anne
> >
> >
> > > -----Original Message-----
> > > From: dumdum 420 [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, January 16, 2003 4:23 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Apache SOAP vs AXIS
> > >
> > >
> > > We are in the process of putting out infrastructure on the
> > > webservice front.
> > >
> > > I need to prepare a report (a little high level )about what are the
> > > difference between the two most common systems used to access the
> SOAP.
> > >
> > > The Apache SOAP and the AXIS. Can anyone help me with this research
> and
> > > compile a document with the difference between the same and
> > > characteristics
> > > of each one of them.
> > >
> > > It will be a great help.
> > >
> > > Thanx in advance . I will compile the document and put it some
> > > where to be
> > > used ... if anybody ever needs it ...!! If there is an exsisting
> > > one already
> > > there kindly redirect me to the URL
> > >
> > > Thanx in advance.
> > >
> > >
> > > Bhanu Pabreja
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _________________________________________________________________
> > > Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> > > http://join.msn.com/?page=features/featuredemail
> > >
> >
> >
> > _________________________________________________________________
> > MSN 8 with e-mail virus protection service: 2 months FREE*
> > http://join.msn.com/?page=features/virus
> >
>
>
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>


_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963