I resolved a very similar problem by decorating the AxisServlet
with my own Servlet which wrapped the HttpServletRequest with a request where
the SoapAction is set (to “”). Could have achieved the same
with a Servlet filter…
CU Christian Seiler
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 20. April
2006 16:09
An: axis-user@ws.apache.org
Betreff: RE: Can you default the
SOAPAction as being ""?
My problem is more simple...
The client that is calling my service is not specifying the SOAPAction at all. I
am using rpc/lit. All of the SOAPActions specified in my WSDL are
"". Empty should not be a problem. Because the client
(which is not under my control) is not specifying a SOAPAction, axis throws an
exception.
Because all of my SOAPActions = "", defaulting the SOAPAction on my
end to "" would solve my problem. Can this be done?
Regards,
Joshua
|
|
kensky <[EMAIL PROTECTED]>
04/20/2006
09:58 AM
Please respond to axis-user
|
To: axis-user@ws.apache.org
cc:
Subject: RE: Can you
default the SOAPAction as being ""?
|
I had a similar problem while client calling. In my scenario there were many
methods which reuses complex types and I used "" as soap action. On
the
client side axis throws exception of EPR and WSA conflict. So, I simply
changed every operations action :) to unique name. Now its working fine.
I dont know what are the consequences of not specifying soap action
header.
Kensky
--
View this message in context:
http://www.nabble.com/Can-you-default-the-SOAPAction-as-being-%22%22--t1475972.html#a4007793
Sent from the Axis - User forum at Nabble.com.
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
