Sanjiva Weerawarana wrote: > > Its been quite a while since we released v2.2 of Apache SOAP. Since then > about 50 bugs have been fixed and there are about another 50 remaining > in the queue (most of them are non-bugs or trivial but some a big). > > I'm interested in doing a v2.3 to try to capture all the fixes that > have been done since 2.2 into a labeled version. Originally it was > intended that v2.2 would be the last as Axis was spsed to take over, > but Axis is now running more than an year late!! However, it looks > like Axis is finally getting nearer to 1.0 status and so putting out > Apache SOAP v2.3 would really allow us to say that's the final verdict > for this codebase. > > I'm willing to serve as release manager and will write up a release > plan. The purpose of this note is to gauge interest on this effort.
+1 A few notes: * I support the notion of a v2.3 without any presumption that it be the "final verdict". * I would encourage you to consider supporting Xerces release 2.0.1; to be more specific, handling isd:map entries in the deployment descriptors. * You might want to take a peek at http://www.apache.org/~rubys/ApacheClientInterop.html to see if there are any low risk items that can be picked off. - Sam Ruby
