> My question is, is this something that the future version of > xml-security will provide? Or is there other way to use > wsu:Id with the xml-security library?
Hardcoding any values into the code is a mistake IMHO. The work-around should probably be to have a system property set by the application to provide the rule to use. This could, I guess, be XPath expressions, or something more constrained like specifying namespace/attribute pairs with an optional containing element namespace/name. I don't know how close the xml:id proposal is to reaching REC status, but getting support for that added will also be critical. -- Scott
