Sam,
IMHO, it isn't worth doing web services unless you use the autogenerated
code. I learned from experience to stop hand jamming xml. If your WSDL
changes, you want to re-autogenerate the plumbing code on both your client
and server side ... and with any luck, any code changes you have are
. No matter what, don't feel bad ...
there is a lot to learn ... and I swear, you can only learn this junk by
doing ...
LOL
cara
On Thu, Apr 2, 2009 at 9:52 AM, Sam Carleton scarle...@gmail.com wrote:
On Thu, Apr 2, 2009 at 11:37 AM, cara pinkgran...@gmail.com wrote:
Sam,
IMHO, it isn't worth doing
I do not use C/C++ server side for production. I have only worked on
'enterprise' systems ... so the web services must be in one of the following
frameworks: J2EE or .NET. I have created the interface with Axis (Java) and
recently JAX-WS. If the guts of my service needed to call C/C++ code, I have
Frank,
Hi again. Just to cover our reasons for using gsoap:
1. It is older software ... fewer bugs. Lower risk for a production project.
2. We used it for an rpc wsdl, so nothing too fancy as far as wsdls go.
3. Our legacy C++ software developers and integration team knows almost
nothing about
We have used gsoap for a scientific C++ app. The documentation is very good.
Our app runs on Solaris and Windows(using mingw). Our gsoap client talks to
an Axis java web service. It was ahead of AxisCpp when we investigated
packages.
http://www.cs.fsu.edu/~engelen/soap.html
On 8/17/07, Frank
Does your generated deploy.wsdd give you any clues?
I have exceptions working with doc/lit wrapped. The typeMapping in my wsdd
file maps MyOwnExceptions to a type (an autogenerated Exception class).
Initially, I had some problems in my namespace mapping, but I'm not sure I
have enough info to
I'd like someone to tell me that Axis2 is ready for prime time. I've jumped
on the list partially to see if Axis2 is ready. But I see enough posts about
Axis2 issues to hang tight with Axis1.4 for now.
cara
On 7/27/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:
If your Axis 1.x services use
I had the same problem. My ServiceLogHandler extends the axis LogHandler. I
can pull normal messages from the MessageContext by implementing the invoke
method. To catch and log exceptions in the handler chain, I had to implement
public void onFault(msgContext).
On 7/23/07, landry soules [EMAIL
