Edwin Goei wrote:
>
> Could you send me the details of the Crimson bug? I am not familiar
> with the other areas.
Gladly. The fix to the problem is:
http://xml.apache.org/websrc/cvsweb.cgi/xml-crimson/src/org/apache/crimson/tree/XmlDocument.java?rev=1.7&content-type=text/vnd.viewcvs-markup
The problem manifests itself on line 98 of:
http://jakarta.apache.org/cvsweb/index.cgi/jakarta-alexandria/proposal/gump/gen.java?annotate=1.2
> As to the various other comments on this thread about breaking
> compatibility, IMO, it is not in anyone's best interest, including
> Sun's, to break compatibility with previous releases. It defeats the
> major value proposition of Java. For example, I've been told that using
> the @deprecated tag is not allowed in new code b/c methods won't ever be
> removed from APIs.
There were methods removed. And there were methods added to public
interfaces that existing code implements.
> So if you find compatibility problems with the JDK 1.4 beta, I'm sure
> the developers would be interested in hearing about them so they can be
> fixed before FCS. A major reason why the software is pre-released as
> beta is to find compatibility problems.
>
> Sorry if I sound overly self-serving b/c I happen to work for Sun.
> There are other times when I don't agree with certain company decisions,
> but that's another topic.
Nothing self-serving about sincerely wanting to avoid compatiblity
problems.
What's the most effective way to get the information to the right people?
I am willing to test new drops on a frequently (even daily) basis.
Alternately, everything required to reproduce my results is freely
available. If someone with the ability to correct these problems is
interested, I am willing to invest the time necessary to show them how to
reproduce the problem
- Sam Ruby
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
