Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: soapAction and .NET interoperability
Date: Wed, 11 May 2005 10:02:58 +0600
Message-ID: <403DD48EAE182940B89ECEAFE03F969002D16661@cs-mailsvr.Virtusa.com>
Thread-Topic: soapAction and .NET interoperability
Thread-Index: AcVUrKVB9NF1IyMcQuWgYAtXXzn1IAAZH4TQABfKBeAAAReIEAAKrYYAAA7psVA=
From: "Samisa Abeysinghe" <SAbeysinghe@virtusa.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>

> Does anybody know of a workaround for this?  Either a way to define my
> service to not require soapAction or a way to=20
> get a .NET client to provide the method name in the soapAction header?

There is no way in Axis C++ to define the service not to require the
SOAPAction as of now. (But we wish to implement such kind of a mechanism
- there is a Jira issue raised on this)

Hence I think you have to figure out how to set the SOAPAction with .net
client. I am not sure how to do this exactly but
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/cpref/=
h
tml/frlrfSystemRuntimeRemotingMetadataSoapMethodAttributeClassSoapAction
Topic.asp may lead to a clue.

Thanks,
Samisa...

-----Original Message-----
From: Yampolsky, Robert [mailto:ryampols@harris.com]=20
Sent: Wednesday, May 11, 2005 2:39 AM
To: Apache AXIS C User List
Subject: soapAction and .NET interoperability

I've seen posted here that Axis services don't work with soapAction set
to "".  I can verify that that's the case.  With no soapAction, I get a
"Soap method is not allowed to invoke" exception, but when I put it in,
I'm able to access the service.  As a matter of fact, it seems to only
require the method (i.e.  soapAction=3D"#METHOD" works just as well as
soapAction=3D"SERVICE#METHOD").

My problem is that I need to interoperate with .NET clients, and they
don't seem to set soapAction (at least by default).

Does anybody know of a workaround for this?  Either a way to define my
service to not require soapAction or a way to=20
get a .NET client to provide the method name in the soapAction header?

Thanks,
Rob