>I thought Java loved XML. Why are XML parsers the biggest pain > in the ass in application development?
Java may love XML but it lacks a good component packaging and versioning solution. That and the complex problems brought about by runtimes with mutliple classloaders will be its eventual downfall. Vlad. P.S. As a random idea, ANT could try to leverage its custom classloader to implement a versioning scheme of some kind, perhaps based on a scheme of standard manifest attributes. There have been experimental efforts to that effect already. Also, perhaps the container-like approach should be driven even further, like in Tomcat (Tomcat's core has access to an XML parser, but the same parser classes are not accessible to individual web apps). But I am sure the team is swamped with requests to implement looping or something :) ... Please respond to "Ant Users List" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> cc: Subject: RE: 1.4.1 JUnit adding jars to classpath behind my back > > Which jar is the problem? Neither jar should contain an XML parser. > Hmm, the problem with XML parsers seems to be a known problem. I am having a similar problem with my test code, since java complains of an incompatible class change, and I cannot fix it without removing crimson.jar from my application classpath. Why is this such a problem? It seems I am always having problems with incompatible xml parsers, and in ant's case it is impossible to remove the "intruding" parser (the one in $ANT_HOME/lib) since it is being used by ant. I thought Java loved XML. Why are XML parsers the biggest pain in the ass in application development? Magnus -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
