[jdom-interest] Xerxes Parser and JDOM

[Jason Hunter]

A couple weeks ago Tobias wrote in complaining that his applet was
always trying to fetch xerces.jar from his server while he was using
crimson.jar as his parser, and wondered why.  I pointed him at the
MANIFEST.MF file.  Seems that was the culprit.

So now we have a decision to make.  Do we

a) Remove the Class-Path line from the MANIFEST.  Upside:  People who
use Crimson won't see two 404 hits.  Downside:  People who use Xerces
will have to explicitly include it in the applet tags.  Further
downside:  The cool "java -jar jdom.jar" easter egg won't work anymore!

b) Keep the Class-Path line.  Upside:  Easy Xerces and cool -jar. 
Downside:  Two wasted hits.

I suspect there may be a third choice, or more upsides/downsides to this
issue, so I'm writing to the list to see if anyone else has a thought.

-jh-

tobias.kaempf at web.de wrote:
> 
> Hi,
> 
> I tried removing the Entry in the META-INF/MANIFEST.MF and it works.
> There is no request for the Xerxes.jar any more on the Network.
> Thanks for this.
> The Entry was in the 3. Row of the File :
> 
> Class-Path: ../lib/xerces.jar xerces.jar
> 
> Tobias Kämpf
> 
> Jason Hunter <jhunter at servlets.com> schrieb am 19.01.02:
> > I suspect it's because in the META-INF/MANIFEST.MF file it refers to
> > xerces.jar.  Try removing that and see if it helps your problem.  If so,
> > we'll have to consider taking that out.
> >
> > -jh-
> 
> ______________________________________________________________________________
> Die schönsten Ski-Regionen der Alpen - jetzt bei Ferienklick.de
> http://ferienklick.de/ski/?PP=2-5-100-105-38