+1 - but can we add the verbage we need to add for the crypto policy?
Cheers,
Berin
Sean Mullan wrote:
Hi all,
It has been almost a year since 1.4.1 was released, and many bugs and
rfes have been fixed and integrated since then. Therefore, I would like
to make a 1.4.2 release available soon, and have at least one or two
beta candidate releases before doing that.
Please let me know if you are ok with this plan:
[ ] +1
[ ] 0
[ ] -1
If -1, please explain why (such as I really need a fix for bug xxxx).
FYI, here are the bugs and rfes that have been fixed since 1.4.1:
Fixed rfe 42653: Add support for C14N 1.1 to Java implementation.
Fixed bug 44205: XMLX509Certificate.getX509Certificate() results in
certificate parsing error.
Fixed Bug 44177: when using xslt transformation there is problem
with xalan newline.
Small refactor for ElementProxy to get rid of the state, it was an
old vestige that where taking space and obfuscating the code.
Fixed bug 40897: String comparisons using '==' causes validation
errors with some parsers.
Fixed bug 43056: Library does not allow specify provider for private
key operations.
Fixed bug 44102: XMLCipher loadEncryptedKey error.
Fixed bug 43239: "No installed provider supports this key" when
checking a RSA signature against a DSA key before RSA key.
Fixed bug 42597: Unnecessary namespace declarations on Signature
children.
Fixed bug 42061: Method to disable XMLUtils.addReturnToElement.
Fixed bug 42865: Problem with empty BaseURI in ResolverLocalFilesystem.
Fixed bug 43230: Inclusive C14n doesn't always handle xml:space &
xml:lang attributes correctly
Fixed bug 38668: Add XMLCipher.encryptData method that takes
serialized data as parameter.
Fixed bug 42866: Error when removing encrypted content in 1.4.1.
Fixed bug 42820: ClassLoader issue causing NoSuchAlgorithmException
loading Provider Implementation.
Thanks,
Sean
