You can also try out gSOAP
http://www.cs.fsu.edu/~engelen/soap.html
Mark Galbreath wrote:
Use C++.NET.
Mark Galbreath
Principal Consultant
Workflow Process Engineering and Systems Integration
http://www.QAT.com
410-703-367 / 800-799-8545
"Never attribute to malice that which can be adequately explained by
stupidity." ~Hanlon's Razor
-----Original Message-----
From: Chris Forbis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 1:18 PM
To: '[EMAIL PROTECTED]'
Subject: RE: client side written in C++
I thought I saw a project for Axis C++ on the Axis page, I am not sure how
much has been done.
-----Original Message-----
From: Ghershony, Arie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 10:55 AM
To: '[EMAIL PROTECTED]'
Subject: client side written in C++
Hi,
My client side will access a webservice written in Axis. However the client
is written in C++, and using Soap API. is it possible to extend Axis API to
C++, and what major issues I might face writing if I dont use Axis on
C++the
client machine.
Thanks,
Arie
-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:02 AM
To: [EMAIL PROTECTED]
Subject: RE: Is it for me? [Was: RE: Axis vs. IBM WSTK vs. Sun Java WSDP]
Daniel,
I suggest that you ask this question on the JXTA list. As I recall, there
were a few folks playing with JXTA and SOAP a while ago.
So what is your goal? To use JXTA as your discovery/connection method? I
certainly don't see any problem transferring a SOAP message using JXTA.
Axis provides a simple transport framework that permits you to use a variety
of transport protocols. So you can use it with HTTP, SMTP, Jabber, etc. I
don't know if anyone on this list has build a transport plug-in for JXTA.
(Note that JXTA isn't really a transport -- it operates at a higher level
and can run over a variety of transports, but I think you could still use
JXTA as a SOAP transport.)
Anne
-----Original Message-----
From: Daniel Elenius [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 4:58 AM
To: [EMAIL PROTECTED]
Subject: Is it for me? [Was: RE: Axis vs. IBM WSTK vs. Sun Java WSDP]
Thank you, Anne, that makes it a bit clearer.
Now, maybe I should say what I need it for. I hope you, or someone
else, can answer these questions. I am working on using WSDL and SOAP
messages with JXTA (www.jxta.org) P2P networks.
I think I can use Axis to easily create WSDL and SOAP messages from
Java code, and the other way around (create Java interfaces of some
sort from WSDL descriptions etc), right?
I don't want to run http or application servers. Does Axis require
this? Is the SOAP in JXTA always used with the HTTP binding? My code
is supposed to run on resource-constrained devices (at least in a
distant future).
Which version of WSDL and SOAP does it support?
regards,
/daniel
On Thu, 2003-02-13 at 03:56, Anne Thomas Manes wrote:
I sound also mention that Macromedia and Borland both distribute
Axis in their products, too.
Anne
-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 8:32 PM
To: [EMAIL PROTECTED]
Subject: RE: Axis vs. IBM WSTK vs. Sun Java WSDP
WSTK includes the binaries (not source) for Axis as well as
wsdl4j, lotusXSL, uddi4j, and wsil4j. See
http://www.alphaworks.ibm.com/aw.nsf/reqs/webservicestoolkit.
Anne
-----Original Message-----
From: Daniel Elenius [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 4:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Axis vs. IBM WSTK vs. Sun Java WSDP
Oh. So WSTK is a proper superset of Axis?
/Daniel
On Wed, 2003-02-12 at 22:03, Doug Davis wrote:
Yes and Yes.
-Dug
Barry Levinson <[EMAIL PROTECTED]> on 02/12/2003 04:00:35 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Axis vs. IBM WSTK vs. Sun Java WSDP
Doesn't IBM WSTK use Axis? Isn't Axis distributed with WSTK?
--Barry
Anne Thomas Manes wrote:
Sun's implementation is not open source. It is a reference
implementation.
The source is available, but it isn't open source. It is
subject to Sun's
source license.
The original Apache SOAP project is based on IBM's
SOAP4J submission.
SOAP4J
was the first published SOAP implementation. It had some
architectural
limitations, so about 2 years ago, the SOAP team decided to
initiate a new
project (Axis). Sun's JAX-RPC project didn't start until
a few months
later.
IBM WSTK is alphaWorks technology. alphaWorks technology is
free, but not
necessarily open source. WSTK runs on either WebSphere or
Tomcat.
Anne
-----Original Message-----
From: Daniel Elenius [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 12:14 PM
To: [EMAIL PROTECTED]
Subject: RE: Axis vs. IBM WSTK vs. Sun Java WSDP
And are Sun's and IBM's runtime environments not open
source?
Does WSTK
require WebSphere to run? If Sun's runtime is open source,
what is the
motivation for this project?
/Daniel
On Wed, 2003-02-12 at 18:04, Anne Thomas Manes wrote:
IBM WSTK is based on Axis.
Both Axis and JWSDP support the JAX-RPC API. The tools are
a
bit different,
though. When you build a client or service with one, you
must deploy it
using that system's runtime environment. For that reason,
I'd recommend
using Axis.
Anne
-----Original Message-----
From: Daniel Elenius [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 11:50 AM
To: [EMAIL PROTECTED]
Subject: Axis vs. IBM WSTK vs. Sun Java WSDP
Hi All!
I am new to web services, and I'd like to ask a newbie
question. I am
doing a project about integrating WSDL/SOAP with JXTA
(www.jxta.org).
How does Axis compare with IBM's Web Services Toolkit and
Sun's Java Web
Services Developer Pack? Are they all compatible somehow?
What features
differentiate them? As I understand, the current JXTA-SOAP
implementation is based on Axis, so I'll probably end up
using that, but
it would be interesting to know the differences.
Regards,
--
Daniel Elenius <[EMAIL PROTECTED]>
--
Daniel Elenius <[EMAIL PROTECTED]>
--
Daniel Elenius <[EMAIL PROTECTED]>
--
Daniel Elenius <[EMAIL PROTECTED]>
