Set my environment to jdk1.3.1_02 simply to eliminate any possibiilty of not being sure which version of xerces is being run - with jdk 1.4 and above properly implementing the endorsed override mechanism to use a specific version of Xerces is required: merely wanted to remove that possibilty as a factor in the equation
As with Tomcat coming with its own version of xerces.jar changing the file by overwriting was simply done to ensure the use of xerces 1.4.4. Very easy to accomplish in Tomcat 4.0.1, once again merely to ensure the proper parser that was stated as being used J> Dave, J> Thanks for taking the time to test this! It's J> actually a problem which one of my co-workers is J> having. After I posted to the group I also replicated J> his environment and found that I couldn't reproduce J> his problem. It's very strange. The only difference J> between our environments is that I was running J> jdk1.4.1 while he was running jdk1.3.1. I was going J> to fall back to 1.3.1 to make sure that that wasn't J> the culprit but I guess now I don't have to bother :) J> I'm pretty sure his InputSource isn't empty as the J> code he sent me was a cut and paste from his servlet. J> Still, it might be useful to know that the stack trace J> is equivalent to one generated by parsing an empty J> string. Thanks again. J> -jason --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
