I was able to solve this by adding in a SOAP Header for the To: that
they were looking for (I was lucky enough to have a working .NET
example, so basically I just mimicked the xml produced by that
application as best I could). Of course now I get a 400 error, but
there's alot more to send
Thanks, Anne.
I'm wondering if there is a way on the client side to signal to the
server that you want it to use the Action in the body of the SOAP
message and ignore the SOAP Actor in the headers?
Jim
Anne Thomas Manes wrote:
Wed, 10 May 2006 06:06:02 -0700
So you should tell the
So you should tell the folks that built the service that they should define a more reasonable Actor attribute. To make it easier for consumers, the Actor attribute should be the same as the service endpoint URL. The wsa:To value specifies the destination property, which is a URI that represents
I am very new to Axis and web services in general. I am writing a
client for a .NET-based web service using the Axis WSDL2Java generator
to create my client. Once I compiled the resulting code and set up a
test program for a very small part of the client, I ran it and got this:
Destination
