hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jason hadoop <jason.had...@gmail.com>
Subject Re: Extending ClusterMapReduceTestCase
Date Wed, 11 Mar 2009 15:01:10 GMT
I am having trouble reproducing this one. It happened in a very specific
environment that pulled in an alternate sax parser.

The bottom line is that jetty expects a parser with particular capabilities
and if it doesn't get one, odd things happen.

In a day or so I will have hopefully worked out the details, but it has been
have a year since I dealt with this last.

Unless you are forking, to run your junit tests, ant won't let you change
the class path for your unit tests - much chaos will ensue.

On Wed, Mar 11, 2009 at 4:39 AM, Steve Loughran <stevel@apache.org> wrote:

> jason hadoop wrote:
>> The other goofy thing is that the  xml parser that is commonly first in
>> the
>> class path, validates xml in a way that is opposite to what jetty wants.
> What does ant -diagnostics say? It will list the XML parser at work
>  This line in the preamble before theClusterMapReduceTestCase setup takes
>> care of the xml errors.
>> System.setProperty("javax.xml.parsers.SAXParserFactory","org.apache.xerces.jaxp.SAXParserFactoryImpl");
> possibly, though when Ant starts it with the classpath set up for junit
> runners, I'd expect the xml parser from the ant distro to get in there
> first, system properties notwithstandng

Alpha Chapters of my book on Hadoop are available

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message