---- you joseph_kesselman wrote ---- > As far as I know, Xalan's only current serious concern with Xerces2 is bug > 6041, which Neil's got a handle on. If the fix for that will be going into > the Xerces2 production release, I'm content; if not, there's a workaround > we could try to apply but I'm just a hair concerned about whether that > workaround could have side-effects elsewhere in Xalan.
Given that it's a clear standards compliance issue, albeit one that only comes up with streams that don't have systemId's set, I would *really* like to see this fixed in the Xerces 2.0.0 gold build. Not only is it a very definite bug, but having to do a workaround in Xalan builds would be 1) dangerous, especially for future maintenance, and 2) difficult to support, since if a user did come up against this problem, it take time to dissect the problem to the point where we say 'ah, that's a known bug; here's the workaround'. Actually the Xalanites do have one other pertinent bug open with Xerces, Bugzilla#6046: although I haven't proven it's a Xerces bug, it only shows up when switching recent Xerces parser code, so it's clearly some change in behavior on the parser's part. More details to follow, I hope. - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]"; "http://www.otnemem.com/"=.sig /> __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
