Apache SOAP is what IBM uses (and originally created... IBM donated it to
Apache a while back).
- James M Snell/Fresno/IBM
Web services architecture and strategy
Internet Emerging Technologies, IBM
544.9035 TIE line
559.587.1233 Office
919.486.0077 Voice Mail
[EMAIL PROTECTED]
Programming Web Services With SOAP, O'reilly & Associates, ISBN
0596000952
==
Have I not commanded you? Be strong and courageous. Do not be terrified,
do not be discouraged, for the Lord your God will be with you wherever you
go.
- Joshua 1:9
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Compare IBM to Apache
For myself I was looking at using apache SOAP on websphere. I was look for
reasons why it would be beneficial rather than just using what IBM
created.
Thanks
-MJ
-----Original Message-----
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Compare IBM to Apache
While this is no definitive, expert comparison, here are some things that
come to mind.
.NET
----
1. Best interop with other .NET, including Microsoft extensions to
standards
2. You can code in nearly every language but Java (with J# coming soon)
3. With Visual Studio.NET, developers barely need to know what they are
doing to get something to mostly work ;-)
4. Runs only on OS platforms supporting .NET (can you guess which ones)
Apache SOAP (really Axis, which is roughtly "Apache SOAP 3.0"
-----------
1. Full source is available
2. Attempts to stick to standards (W3C, IETF, JCP, OASIS, etc.)
3. Client runs on all platforms supporting J2SE, server on J2EE subset
WebSphere
---------
1. Based on Axis (I hope)
2. Tools to help developer that are not built into Axis
To me, the big question is whether you want to be limited to deploying
SOAP
services on Wintel platforms, which the decision to go with .NET
effectively
does. Yes, I know, Microsoft is releasing a source reference
implementation
on FreeBSD (which cannot be used for commercial development) and Ximian is
working on a portable .NET based on ECMA specs, but it's hard to imagine
significant .NET adoption anywhere but Win32.
You should also note that, in the Java world, there are implementations
beyond Axis and WebSphere. FWIW, eWeek just ran a glowing review of WASP
from Systinet, for example.
Scott Nichol
----- Original Message -----
From: "Johnson, Michael1 [IT]" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 01, 2002 08:47
Subject: Compare IBM to Apache
> What are the advantages to using apache SOAP vs say IBMs SOAP bundled
with
> websphere or MS SOAP bundled with .NET?
>
> -MJ
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
