> 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 is getting rather ugly, with calls > all over the place to enable and disable functionality. I am thinking > of introducing a set of methods in 1.2 that will provide a consistant, > single interface for all configuration on DSIGSignature, as this will > provide better portability. I'll also add the interface to XSECProvider > to allow for "global" configurations. Half the work was done for 1.1 in > that there is now an "environment" object that holds all this > information and gets passed around the various signature objects. > > Interested in thoughts on the last part. Seems like a good idea to me. I'm not working off of that modified code yet (using 1.0) so I can't comment specifically on the environment object, but that seems like a reasonable way to provide options to the signature wrapper. -- Scott
