Elena, Great Question!!! Here's more: We are opening a can of worms...
- Are we going to force "EVERYONE" to fix their code? - Will this make it difficult for people to migrate to Xerces2? - Should this be a FAQ? - Should the AttributesImpl.java in SAX be fixed to check for Nulls? - Should all external code in Xerces2 like DOM/SAX etc be reviewed for this case? - Should we migrate to xml-commons? Thanks, dims --- Elena Litani <[EMAIL PROTECTED]> wrote: > > > Davanum Srinivas wrote: > > > NullPointerException. This is due to the URI that is stored...In Xerces2 getURI() >returns > null, in > > Xerces1 getURI() returns an empty string. If you need more information, shoot me a >mail. > > In Xerces2 we've decided to use null instead of empty string for URI. > As a temporary solution, I can fix the problem in AbstractSAXParser > (getURI() - to return "" instead of null). > However, I am not sure that this is right - I believe that the problem > is in SAX definition. > Why is it required that URI would be an empty string, which btw is not a > legal URI? > > -- > Elena Litani / IBM Toronto ===== Davanum Srinivas - http://jguru.com/dims/ __________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
