Hi, Answers inline.
> I have been looking at upgrading our xmlsec dependency to 2.2.0, on the > basis that at some point the 2.1.x series will lose support. Is that > already the case? Not obvious from the web site at present. > It's not already the case, there will be at least a 2.1.6 release at some point. > > Anyway, I ran into an issue with method signatures that I am not sure was > intended in 2.2.0. It seems to have come about from this issue: > > It doesn't seem to me as if this was intentional (given the Javadoc allows > the original method to be passed a `null`), and the Jira ticket doesn't > discuss adding new methods. I guess I'd be interested to know what the > thinking was here, whether this was intentional and whether it might make > sense to fix the regression in a future 2.2.x release. > Yes good catch, it was not intentional to have a conflict between the two methods. For now you can upgrade just by casting null to a String. Any change I make to the method signatures for 2.2.1 will break backwards compatibility. So for 2.3.0 I will fix it by re-ordering the parameters for the Serializer case. Colm. > > Cheers, > > -- Ian > > > > >
