|
From: Watkins, D. <dav...@fa...> - 2004-10-26 10:03:03
|
>=20 > Hhm, I'm not sure if exposing Xerces might have side effects,=20 > e.g. with other plugin shipping with a different version of=20 > Xerces like XmlBuddy. > Not sure, I thought the way Eclipse handles plugin=20 classpaths should prevent this scenario.... =20 > Is it sufficient for you to use the built-in XML parser of=20 > JDK 1.4 (Apache Crimson)? > The only reason why Spring IDE core ships with it's own copy=20 > of Xerces is because Crimson doesn't support DOM level 3. > ....however this is probably a better idea. I'll look into it. =20 Was thinking of using an alternative approach anyway, so I can=20 avoid the 'unwanted optional attributes' problem I was talking=20 about in an earlier posting. Cheers, dw |