Everyone,
I think this is a great idea, however could I just confirm that the bug to
do with accessing a JAXP debug security property (I'm sorry I can't
remember the exact line) that was stopping Apache SOAP working in
(non-signed) Java applets, and yet seemed a pretty easy fix, has been
addressed? It seems to come and go with different versions of 2.2, but I'd
just like the peace of mind of knowing that somebody has definitely fixed
it :)
Many thanks,
Richard.
Raghavan
Srinivasan To: [EMAIL PROTECTED]
<raghavan@ipl cc: [EMAIL PROTECTED]
anet.com> Subject: Re: do an Apache SOAP 2.3
release ?
27/04/2002
03:12 AM
Please
respond to
soap-user
Hi Sanjiva ,
This makes a lot of sense to me . For folks that have been
using / certifying their applications with the 2.2 release(and have not
yet adopted Axis) , handling bugs / features introduced in future
builds means having to go through cvs and figure out exactly which files
changed and patch them in .
e.g i am still trying to locate all the files changed to support the
switching the Current Schema version to 2001 .
Simply changing Constants.java does not solve the problem completely .
This is ugly and when customers are involved , there is the greater risk
that if they make their own
changes in the 2.2 install to support their own app specific changes ,
they might overwrite the changes shipped out to them .
Having a 2.3 release will bring in all such changes over the last year
into one version .
Thanks -
Raghavan
Sanjiva Weerawarana wrote:
>Hello,
>
>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.
>
>Thanks!
>
>Sanjiva.
>
