Ken said:
> I mapped the url-pattern 'services/*' to a very simple filter that
> stuffs a SOAPAction
> with an empty string value whenever one isn't sent by the caller.
>
You probably should stuff it with no value rather than an empty string.
Per the spec (http://www.w3.org/TR/SOAP/#_Toc478383528
re is nothing in the specification that requires a
SOAP server to respond with a fault.
Anne
> -Original Message-
> From: Chris Forbis [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 27, 2002 1:47 PM
> To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: RE: SOAPAc
s 1.2, why
not
make it an option in the config? Require or not to require?)
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 6:38 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: SOAPAction HTTP header required (again)
In SOA
]
Subject: RE: SOAPAction HTTP header required (again)
In SOAP 1.1, the SOAPAction header is required, although the contents can be
empty.
In SOAP 1.2, the SOAPAction header is optional.
Anne
> -Original Message-
> From: Xander van der Merwe [mailto:[EMAIL PROTECTED]]
> Sent
IL PROTECTED]
> Subject: Re: SOAPAction HTTP header required (again)
>
>
> Ok, according to SOAP1.1 it looks like it is required. It would
> not be a bad
> idea to put this into the Axis FAQ since it is one of the biggest gotchas
> for any Axis newby. It took me a while anyway, to figu
The trouble is that we are often writing services to be vended to
clients
over which we have no control - and the client tool vendors don't seem
to interpret
it as being required.
- Ken
On Tuesday, November 26, 2002, at 04:46 PM, Xander van der Merwe wrote:
Ok, according to SOAP1.1 it looks l
to:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 5:19 PM
To: '[EMAIL PROTECTED]'
Subject: RE: SOAPAction HTTP header required.
I have seen this before, I have wondered why an action is needed. I
have
MANY client tools that will not allow a action to be set, and for
those I
ha
Ok, according to SOAP1.1 it looks like it is required. It would not be a bad
idea to put this into the Axis FAQ since it is one of the biggest gotchas
for any Axis newby. It took me a while anyway, to figure out how to get the
MS Soap Client to work with Axis due to this requirement.
Xander
-
I don't know of a way to avoid this, other than to change the Axis code to
not throw an exception when the SOAPAction is empty. This might not be a bad
idea as I believe the that the usage of the SOAPAction has not been
formalized yet. On the client side (using the MS SOAP toolkit) I got around
thi
: Chris Forbis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 5:19 PM
To: '[EMAIL PROTECTED]'
Subject: RE: SOAPAction HTTP header required.
I have seen this before, I have wondered why an action is needed. I have
MANY client tools that will not allow a action to be set, and
I have seen this before, I have wondered why an action is needed. I have
MANY client tools that will not allow a action to be set, and for those I
had to make a proxy to get the message, then convert it and resend with the
action = "" set.
Am I missing a simple way to turn off this need?
-Or
11 matches
Mail list logo
