Would it be useful to have the ability to have name based Id searching
turned off?
In a release, yes, I would probably turn it off. I probably wouldn't be
relying on anything until it's officially out, so there's no need to rush
anything in on my account.
-- Scott
2. Allowable names for Id attributes are now stored in a list. This
list can be added to by the calling program using new methods on
DSIGSignature.
I like this. It lets you work around situations where you don't have DOM3
support, in Java especially.
As an aside, the DSIGSignature class
2. Allowable names for Id attributes are now stored in a list. This
list can be added to by the calling program using new methods on
DSIGSignature.
I like this. It lets you work around situations where you don't have
DOM3 support, in Java especially.
Which is a good point. I have only
Given the Java library is unlikely to happen this weekend (unless people
help - hint hint :), do people think we should try to get this ID
handling functionality into it prior to a release?
I'm agnostic, since I don't generally rely on unreleased functionality. I'm
already using DOM3 calls for
Given the Java library is unlikely to happen this weekend (unless
people help - hint hint :), do people think we should try to get this
ID handling functionality into it prior to a release?
I'm agnostic, since I don't generally rely on unreleased functionality.
I'm already using DOM3 calls
Just to follow up this rather old thread.
I have just checked an update into CVS for the C++ library around the
handling of Id attributes, implementing the following.
1. A method on DSIGSignature allowing the caller to control whether the
library will search for Ids based on names if a call
