Looking at soap headerblock[1] it doesnt talk about namespace
qualification of the attributes on header blocks. I think it should
follow the schema definition of the element that goes as header block.
I think only thing it requires is the namespace qualification of the
element information item that goes as header block:
"MUST have a [namespace name] property which has a value, that is the
name of the element MUST be namespace qualified."
-vivek.
[1]
http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#soapheadblock.
Kohsuke Kawaguchi wrote:
> Arun Gupta wrote:
>> A quick question on schemas ...
>>
>> Are the following two instances of SOAP 1.2 headers equivalent ?
>>
>> <ck:CustomerKey xmlns:ck="http://example.org/customer"
>> xmlns="http://www.w3.org/2005/08/addressing"
>> IsReferenceParameter="1">Key#123456789</ck:CustomerKey/>
>>
>> <ck:CustomerKey xmlns:ck="http://example.org/customer"
>> xmlns:wsa="http://www.w3.org/2005/08/addressing"
>> wsa:IsReferenceParameter="1">Key#123456789</ck:CustomerKey>
>
> No. In particular the former @IsReferenceParameter is really
> @{}IsReferenceParameter, while the latter is
> @{http://www.w3.org/2005/08/addressing}IsReferenceParameter
>
>> The question is, does the attribute in a SOAP header MUST always be
>> namespace qualified ?
>>
>> SOAP 1.2 [1] requires AII to be namespace qualified. Does it mean
>> they always MUST be prefixed by a namespace or the namespace
>> defaulting rules would apply as well ?
>>
>> I could not find a similar requirement in SOAP 1.1.
>>
>> [1] http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#soaphead
>>
>> -Arun
>>
>
>
--
Vivek Pandey
Web Services Standards and Technologies
Sun Microsystems Inc.