You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by robert <ro...@gmail.com> on 2006/04/19 20:16:40 UTC
Re: Can you default the SOAPAction as being ""?
Sure, soap action can be "" . However, that typically is only valid for a wsdl
using RPC encoded style. I've never seen Doc / lit wsdl without a soap
action.
HTH,
Robert
http://www.braziloutsource.com/
Em Quarta 19 Abril 2006 15:08, o Joshua.White@hartfordlife.com escreveu:
> Can you configure axis to default the SOAPAction as being ""? I have a
> client which is sending me a message without the SOAPAction header.
>
> Joshua
>
> *************************************************************************
> 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.
> *************************************************************************
--
Re: Can you default the SOAPAction as being ""?
Posted by Eran Chinthaka <ch...@opensource.lk>.
Hi Justin and Robert,
Seems I have missed this thread. Please give me an executive summary or
try (again) to file a JIRA. May be I can help :)
- Chinthaka
Justin Schoeman wrote:
> Axis2 no longer reports an EPR not found error - it just assumes the
> wrong operation to be performed... Tried to file a JIRA, but connection
> timed out, and threw away 15minutes of typing, so gave up ;-) .
>
> -justin
>
>
> robert lazarski wrote:
>> ...
>> As a side note, I'll test the latest svn for axis2 to see if it
>> handles "" for soapAction. If it doesn't, from what the spec says
>> I guess I need to file a jira.
>
Re: Can you default the SOAPAction as being ""?
Posted by Justin Schoeman <ju...@expertron.co.za>.
Axis2 no longer reports an EPR not found error - it just assumes the
wrong operation to be performed... Tried to file a JIRA, but connection
timed out, and threw away 15minutes of typing, so gave up ;-) .
-justin
robert lazarski wrote:
> ...
> As a side note, I'll test the latest svn for axis2 to see if it handles
> "" for soapAction. If it doesn't, from what the spec says I guess I
> need to file a jira.
Re: Can you default the SOAPAction as being ""?
Posted by robert lazarski <ro...@gmail.com>.
I was hoping for someone to jump in and quote the spec ;-) . All I said was
"I've never seen Doc / lit wsdl without a soap
action" . Actually I had some problems with Axis2 with a "" for a soap
action throwing "Operation Not found" for which I created this jira:
http://issues.apache.org/jira/browse/AXIS2-317?page=all
I realize the poster is talking about 1.x , however. My basic point still
stands though: "" is typically the value of the soapAction for RPC / encoded
wsdl - from what I have seen. The value of soapAction for doc / lit and rpc
/ lit is typically not "" - though I now know the spec states it can be -
thanks for the tip.
As a side note, I'll test the latest svn for axis2 to see if it handles ""
for soapAction. If it doesn't, from what the spec says I guess I need to
file a jira.
Thanks,
Robert
http://www.braziloutsource.com/
On 4/19/06, Dies Koper <di...@jp.fujitsu.com> wrote:
>
> Hello Robert,
>
> Your comment sounds like your saying that an empty soap action ("") is
> not valid for RPC/literal and DOC/literal. That's not what you mean, is
> it?
>
> The WS-I BP1.0 spec uses an empty soapAction in its examples to denote a
> correct, interoperable value. The WS-I BP1.0 applies to WSDLs of style
> RPC/literal and DOC/literal.
>
> CORRECT:
>
> A WSDL Description that has:
>
> <soapbind:operation />
>
> or
>
> <soapbind:operation soapAction="" />
>
> results in a message with a corresponding SOAPAction HTTP header field
> as follows:
>
> SOAPAction: ""
>
> As far as I know, Axis's stubs will set the SOAPAction header to
> whatever is defined in the corresponding soapAction attribute in the
> WSDL, and the server will complain when it is not set ("" is fine, but
> nothing is a no-no).
>
> Regards,
> Dies
>
>
> robert wrote:
> > Sure, soap action can be "" . However, that typically is only valid for
> a wsdl
> > using RPC encoded style. I've never seen Doc / lit wsdl without a soap
> > action.
> >
> > HTH,
> > Robert
> > http://www.braziloutsource.com/
> >
> > Em Quarta 19 Abril 2006 15:08, o Joshua.White@hartfordlife.com escreveu:
> >> Can you configure axis to default the SOAPAction as being ""? I have a
> >> client which is sending me a message without the SOAPAction header.
>
>
>
Re: Can you default the SOAPAction as being ""?
Posted by Dies Koper <di...@jp.fujitsu.com>.
Hello Robert,
Your comment sounds like your saying that an empty soap action ("") is
not valid for RPC/literal and DOC/literal. That's not what you mean, is it?
The WS-I BP1.0 spec uses an empty soapAction in its examples to denote a
correct, interoperable value. The WS-I BP1.0 applies to WSDLs of style
RPC/literal and DOC/literal.
CORRECT:
A WSDL Description that has:
<soapbind:operation />
or
<soapbind:operation soapAction="" />
results in a message with a corresponding SOAPAction HTTP header field
as follows:
SOAPAction: ""
As far as I know, Axis's stubs will set the SOAPAction header to
whatever is defined in the corresponding soapAction attribute in the
WSDL, and the server will complain when it is not set ("" is fine, but
nothing is a no-no).
Regards,
Dies
robert wrote:
> Sure, soap action can be "" . However, that typically is only valid for a wsdl
> using RPC encoded style. I've never seen Doc / lit wsdl without a soap
> action.
>
> HTH,
> Robert
> http://www.braziloutsource.com/
>
> Em Quarta 19 Abril 2006 15:08, o Joshua.White@hartfordlife.com escreveu:
>> Can you configure axis to default the SOAPAction as being ""? I have a
>> client which is sending me a message without the SOAPAction header.
RE: Can you default the SOAPAction as being ""?
Posted by kensky <ke...@googlemail.com>.
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.