Apache SOAP supports the original SOAP Messages with Attachments (http://ws.apache.org/soap/docs/index.html) specification. This uses the MIME standard. Many SOAP implementations support this.
The notable exception is Microsoft, which, despite having contributed to the SOAP Messages with Attachments specification, only supports attachments using DIME. As such, Apache SOAP cannot exchange attachments with Microsoft SOAP clients and servers. Apache Axis, on the other hand, implements attachments using both MIME and DIME, and thus can interoperate with Microsoft, as well as with the implementations that work with Apache SOAP. Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Bassem HAIDAR" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 1:08 PM Subject: Re: Apache SOAP VS Apache AXIS hello Would Apache Axis work well for file attachmenet then Apache Soap ? thanks Secka-Jallow, Dibor wrote: > I have a windows XP machine. Would Apache Axis work on windows XP > environment? > > Dibor Secka-Jallow > Web Developer > Atlanta Housing Authority > [EMAIL PROTECTED] > 404-817-7370 > > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 1:03 PM > To: [EMAIL PROTECTED] > Subject: Re: Apache SOAP VS Apache AXIS > > If you do not have considerable time invested in this and do not have > services running in production, I highly recommend you change to Axis > now. Apache SOAP is best for people who have already made a significant > commitment. > > You will want to use the 1.1 version of Axis at > http://ws.apache.org/axis/download.cgi. The binary distribution is best > for most users. The source distribution requires that you build Axis > yourself. It is most useful if you are the type of user who wants to > investigate bugs or make modifications on your own, or if you find the > API documentation incomplete and want to use the source to fill the > gaps. > > Personally, I started Apache SOAP using both. The binaries are what I > deployed, and the source was useful for going beyond the documentation > to understand what was really happening under the covers. > > Scott Nichol > > Do not send e-mail directly to this e-mail address, > because it is filtered to accept only mail from > specific mail lists. > ----- Original Message ----- > From: "Secka-Jallow, Dibor" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, February 25, 2004 11:48 AM > Subject: RE: Apache SOAP VS Apache AXIS > > > I do have existing Apache soap code written my notepad. What should I > do now? > > Dibor Secka-Jallow > Web Developer > Atlanta Housing Authority > [EMAIL PROTECTED] > 404-817-7370 > > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 11:48 AM > To: [EMAIL PROTECTED] > Subject: Re: Apache SOAP VS Apache AXIS > > If you do not have existing Apache SOAP code, you should definitely use > Axis. Here are some reasons. > > 1. The Apache SOAP project has almost no active development, and has not > had a new release in years. > > 2. Axis supports more web services specifications and intends to > implement new ones as they come up. Right now, the most important of > the implemented specifications is WSDL 1.1, which is critical to smooth > interoperability. It also implements JAX-RPC, meaning other Java > implementations supporting that spec can be interchanged with it, DIME, > which makes its attachments interoperable with Microsoft, and HTTP 1.1. > > 3. As partially covered in point 2, Axis has more extensive > interoperability with other SOAP implementations. > > Scott Nichol > > Do not send e-mail directly to this e-mail address, > because it is filtered to accept only mail from > specific mail lists. > ----- Original Message ----- > From: "Calicrates Policroniades" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, February 25, 2004 10:54 AM > Subject: Apache SOAP VS Apache AXIS > > > > Hi, > > I'm at the beginning of a software project in which I'm planning to > include > support for SOAP messages in an application with intensive typed data > interchange. I've been reading the FAQs and documentation available and > all of > them seem to be quiet sympathetic with apache soap's follow-on project > Apache > AXIS. I understand the why of this in general terms, but I was wondering > if > someone with more experience than me (I'm a newbie to be honest) can > still > find advantages in using apache SOAP and not axis. > > Thanks, > Cali > > > > > >
