You are right, +1 to 1.4 then... The only thing is that we should said that 1.3 is not recomended to be used in multi threads services :( .
On 5/4/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1 to 1.4 On 5/4/06, Sean Mullan <[EMAIL PROTECTED]> wrote: > Hi Raul, > > Raul Benito wrote: > > Hi, > > > > I'm planning to do a minor release of java xmlsec 1.3.1. The main > > reason, is the bug > > http://issues.apache.org/bugzilla/show_bug.cgi?id=38605 , that hits > > when the library is used in multithreads and use X509 resolvers, > > resolving this has change slightly the API of the resolvers (see the > > comment #3 in the bugzilla entry). But there are more bugfixes, and > > some small optimizations (I don't like to do releases with > > optimizations but this is how the things gone), The Changelog so far > > is: > > Fixed bug 38655 > > Fixed bug 38444. > > Fixed bug 38605. > > Fixed bug 39200 > > Refactored the way keyresolver works instead of calling > > canResolve/resolveX only resolveX is used and if it returns null it > > means it cannot resolve. > > Minor Performance Opts(see http://r-bg.com/2005/Dec/26 & > > http://r-bg.com/2006/Jan/14 for more info). > > > > > > So what do you think of doing a release 1.3.1, or do you think the API > > changes leads to a 1.4 release? > > I'm all in favor of doing a release, but it should probably be 1.4 since > JSR 105 has been integrated and this would be a major new feature. > > I think I fixed a few other bugs but haven't updated the changelog, I'll > do so. > > --Sean > > -- Davanum Srinivas : http://wso2.com/blogs/
-- http://r-bg.com
