[EMAIL PROTECTED] wrote:
If the latter, how to cope with definitions like this <doc> <a:b a="uri3"/> <a:a a="uri1"> <a:ToBeSigned a="uri2"/> </a> </doc>
what's the value of the prefix a?
All in All it seems is easier if you put all namespace definitions you need in the signature element.
Exactly - or at least in scope for teh XPath transform (using c.setXpathNSContext or whatever the call is :>)
And in fact the intent of the spec is that the XPAth is evaluated in the context of the point in the document in which the XPath is embedded to get past exactly the problem you document above.
Cheers,
Berin