[jdom-interest] Xerxes Parser and JDOM

[Jason Hunter]

Sounds reasonable.

This isn't the first time I've had to stop using XML because it was more
trouble than it was worth managing the parser classes.  Too bad.

<moment of silence for our lost coolness>

-jh-

james todd wrote:
> 
> i second this view.
> 
> when i saw the initial write-up on this one it explained a ton
> as to why, at times, we need to include xerces.jar in our deployment
> container's classpath ... when we long since moved to crimson.
> 
> my view is this is an artifact. i too like the feature it provided
> in one scenario but i see no way to provided the same feature for
> all scenarios with no ill effect.
> 
> - james
> 
> Alex Rosen wrote:
> >
> > Realistically, here's really no good reason that the aboutbox/easteregg uses
> > XML at all, except that it's cool. And it's not really correct that jdom.jar
> > should favor xerces.jar over any other parser. While I'm not *always* in
> > favor of correct over cool, I think in this case we should go with plan A,
> > and make the about box just spit out the contents of a text file instead.
> >
> > Alex
> >
> > > -----Original Message-----
> > > From: jdom-interest-admin at jdom.org
> > > [mailto:jdom-interest-admin at jdom.org]On Behalf Of Jason Hunter
> > > Sent: Friday, January 25, 2002 7:38 PM
> > > To: JDOM Interest
> > > Cc: tobias.kaempf at web.de
> > > Subject: Re: [jdom-interest] Xerxes Parser and JDOM
> > >
> > >
> > > 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
> > > _______________________________________________
> > > To control your jdom-interest membership:
> > > http://lists.denveronline.net/mailman/options/jdom-interest/yo
> > uraddr at yourhost.com
> >
> > _______________________________________________
> > To control your jdom-interest membership:
> > http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com