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
From: "Ken Pelletier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 27, 2002 11:14 AM
Subject: SOAPAction HTTP header required.
I have a service which I've moved from Apache SOAP to Axis and am now
testing.
Apart from a couple of things, it&#
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
- Original Message -
From: "Ken Pelletier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 27, 2002 11:14 AM
Subject: SOAPAction HTTP header required.
> I have a service which I've moved from Apache SOAP to Axis and am now
> testing.
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 27, 2002 11:14 AM
Subject: SOAPAction HTTP header required.
> I have a service which I've moved from Apache SOAP to Axis and am now
> testing.
>
> Apart from a couple of things, it's working qu
: 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
this need?
-Original Message-
From: Ken Pelletier [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 5:15 PM
To: [EMAIL PROTECTED]
Subject: SOAPAction HTTP header required.
I have a service which I've moved from Apache SOAP to Axis and am now
testing.
Apart from a couple of thing
I have a service which I've moved from Apache SOAP to Axis and am now
testing.
Apart from a couple of things, it's working quite well.
I have one instance where a particular client application can no longer
make calls to the service now that it's been placed under Axis, but
could when it was u
12 matches
Mail list logo
