> What I actually wanted to know was whether the XMLSec implementation of > Transforms in general and Filter2 in particular, by default, supports > locating elements that have a namespace prefix.
Yes, it does, but I'm guessing (but could be wrong) the canonicalizer may be stripping your prefix definition out because it isn't used within the Signature element outside of the Qname in the element value. The solution to that is the <InclusivePrefixes> element parameter inside the <Transform> to force the inclusion. But when I tried it 2 years ago, xmlsec didn't support that. > If not, am I supposed to provide the prefix mappings myself to a container > like XPath2FilterContainer via adding new ns attributes with the > 'setXPathNamespaceContext' method? Is this processing model correct? I don't think so. -- Scott
