Jacob Kjome <[EMAIL PROTECTED]> wrote on 10/02/2006 01:03:48 PM: > Quoting "Crain, David B. (LNG-DAY)" <[EMAIL PROTECTED]>: > > > > > > 1) What version of the JDK/SDK was used to build the latest > > version of Xerces jars. I am referring to the following download site: > > http://www.apache.org/dist/xml/xerces-j/ > > Did you try looking at the xercesImpl.jar MANIFEST.MF? It says... > > Created-By: 1.3.1 (IBM Corporation) > > Not sure about the rest below. However, I don't think the JDK used to compile > the code should have much (any?) effect on performance at runtime. I suppose > newer compilers might optimize the bytecode a little better. In any case, > Xerces is compiled with a lowest-common-denominator JDK so that (I presume. > Note I'm not a Xerces project team member, so this is my own $0.02)... > > 1. It can run in the earlier JDK's as well as the newer ones. Setting the > "target" and "source" compile options are another way to do this, but that > doesn't solve #2... > 2. Newer API's aren't accidentally introduced.
Right. And sometimes it isn't obvious that you're pulling in newer APIs. For instance if you're compiling the following on JDK 1.3, a.append(b) calls StringBuffer.append(Object). On JDK 1.4 that call will be bound to StringBuffer.append(StringBuffer) instead and you'll get a NoSuchMethodError if you then try executing it on JDK 1.3. StringBuffer a = ...; StringBuffer b = ...; a.append(b); There was code like this in the serializer at one time. > Jake > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
