Ops, i overlook this post.
To make soapAction work you need to use
<method name="Login" soapAction="Login" >
Attribute name is "soapAction" not "action".
On 6/1/07, MattJax <[EMAIL PROTECTED]> wrote:
Hi,
I've been battling to try and get Aegis to generate the SOAPaction in the
HTML header as I'm communicating with a .NET WS which won't accept an empty
SOAPaction . In my mappings, I've got:
<method name="Login" action="Login" mappedName="Login">
and in my client I've got:
ObjectServiceFactory factory = new ObjectServiceFactory();
AegisServiceConfiguration conf = new AegisServiceConfiguration();
conf.setServiceFactory(factory);
factory.getServiceConfigurations().add(conf);
This still generates an empty SOAPaction. I'm running xfire 1.2.6 on Java
1.4 (got to stay with 1.4 for now...)
Any idea what else I should try?
Thanks in advance,
Matt
Tomek Sztelak wrote:
>
> You need to add AegisServiceConfiguration to your factory :
> factory.getServiceConfigurations().add(0, conf);
> Of course you can also do it in your services.xml file :)
--
View this message in context:
http://www.nabble.com/SoapAction-tf3703322.html#a10913065
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
