Hello,
I have recently encountered the issue described at
https://issues.apache.org/jira/browse/WSS-148 and am wondering if it doesn't
make sense to allow for the Type attribute to be namespace qualified.
I've examined Page 8 of the Web Services Security, UsernameToken Profile 1.1
spec and while
equiring Type to be
> namespaced.
>
> That being said, the reality is what it is. I wonder if WSS4J devs would
> accept some kind of MS-compatibility mode that is turned off by default but
> can be turned on for WCF interoping deployments (may be via configration)...
>
&g
not implictly inherit the namespace of its element [1]. According
> to the specs, attributes "wsse:Type" and "Type" are two different entities.
>
> George
>
>
> [1] http://www.w3.org/TR/xml-names/#uniqAttrs
>
> --
> *From:* Mar
4J then do? Is it
> a "MS misbehaviour" and interpret it as the standard password type
> or leave interpretation and handling to the specific implementation?
>
> That's why XML has name spaces and why implementation must use
> name spaces in the correct way.
>
