DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302 Sealing Violation ------- Additional Comments From [EMAIL PROTECTED] 2001-12-11 18:16 ------- >A part of me does wonder how Ant and other Xml tools out there expect to deal >with Java once 1.4 becomes official and more widespread, since it includes JAXP >and Crimson automatically, which results in killing, effectively, the "market" >such as it is for Xerces and other parsers (sure, you could override the >property and use something else, but who would? that's how Microsoft has taken >over everybody's lives these days...), when java1.4 becomes official we will at least have standardisation; java1.4 implies a known set of libraries, and no need to redist a version of jaxp or crimson. You can still redist xerces, and there will still be valid reasons, cos JAXP does let you add in extra parsers, *provided* they are visible in the same classloader that JAXP loads in. Longer term things get interesting; there will be no way to provide upgrades to JAXP/crimson in the run time without doing a full upgrade of the JRE; Provided the XML parser does everything you want, reliably, this is not an issue. But with all the different successors to DTDs, from simple ones to XSD, which seems a conspiracy to make XML parsers harder to write, there could be problems with this approach. It depends on the frequency of bugs vs. the frequency of JRE upgrades. One thing that wont be possible will be to redist a version of the parser to fix a particular bug in your code, which may be what JAXB is doing... To compare with the microsoft approach, MSXML is a versioning nightmare of all its own, with a different server side version from a client side, the whole COM versioning model still being broken, etc. .NET provides its own version for a reason. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
