Issue with dependency on XML

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Issue with dependency on XML

Alexandru Popescu ☀

Hi all!

Today I've hit an ugly problem when trying to use TestNG along with an
application depending on some XML jars (xerces and xml-apis). The
problem was caused by JUnitXMLReporter which in the mentioned
environment just exploded when hitting the line:

Transformer transformer= TransformerFactory.newInstance().newTransformer();

And I think I remember other people complaining about a similar
problem in the past.

Now on the good side of the story: I've been able to quickly write a
new JUnit XMLReporter which doesn't depend on any XML libraries, just
by using the internal XMLStringBuffer. I have verified it against a
couple of JUnit tests (passing and failing) and it behaves correctly.

My proposal is to replace the reporter depending on XML libraries with
the new one. If there are any arguments against this please let me


.w( the_mindstorm )p.
  TestNG co-founder
EclipseTestNG Creator

You received this message because you are subscribed to the Google Groups "testng-dev" group.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to [hidden email]
For more options, visit this group at