Re: JUnit test failure

2004-02-12 Thread Finn Bock
[J.Pietschmann]

Hi all,
I get a nice Junit failure:
Testcase: testFO2PDFWithDOM took 0.23 sec
Caused an ERROR
loader constraints violated when linking org/w3c/dom/Node class
java.lang.LinkageError: loader constraints violated when linking
This seems to have something to do mixing Jars form the JDK and
fop/lib. Does anybody have an idea how this can be avoided?
Any new information on how to avoid this error? Or perhaps a description 
of an environment where it doesn't occur.

I can't make the hint in the junit faq work for me. I also think 
junit3.8.1 already have the lines in its excluded.properties.

regards,
finn


Re: JUnit test failure

2004-02-09 Thread Christian Geisert
J.Pietschmann wrote:
Hi all,
I get a nice Junit failure:
Testcase: testFO2PDFWithDOM took 0.23 sec
Caused an ERROR
[..]

This seems to have something to do mixing Jars form the JDK and
fop/lib. Does anybody have an idea how this can be avoided?
I had a similar problem with JUnit/Log4J some time ago
See http://junit.sourceforge.net/doc/faq/faq.htm#running_9
--
Christian


Re: JUnit test failure

2004-02-09 Thread Jeremias Maerki
I got another one. Probably a Xerces version problem. No good idea for
both problems, I'm afraid.

org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or
change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(Unknown Source)
at org.apache.xerces.dom.AttrNSImpl.setName(Unknown Source)
at org.apache.xerces.dom.AttrNSImpl.init(Unknown Source)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(Unknown Source)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(Unknown Source)
at org.apache.xml.utils.DOMBuilder.startElement(DOMBuilder.java:339)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown 
Source)


On 07.02.2004 23:56:40 J.Pietschmann wrote:
 Hi all,
 I get a nice Junit failure:
 Testcase: testFO2PDFWithDOM took 0.23 sec
   Caused an ERROR
 loader constraints violated when linking org/w3c/dom/Node class
 java.lang.LinkageError: loader constraints violated when linking
   org/w3c/dom/Node class
   at org.apache.xalan.transformer.TransformerIdentityImpl.
createResultContentHandler(TransformerIdentityImpl.java:186)
   at org.apache.xalan.transformer.TransformerIdentityImpl.
transform(TransformerIdentityImpl.java:296)
   at org.apache.fop.BasicDriverTestCase.
loadDocument(BasicDriverTestCase.java:133)
   at org.apache.fop.BasicDriverTestCase.
testFO2PDFWithDOM(BasicDriverTestCase.java:149)
 
 This seems to have something to do mixing Jars form the JDK and
 fop/lib. Does anybody have an idea how this can be avoided?



Jeremias Maerki



Re: JUnit test failure

2004-02-09 Thread J.Pietschmann
Jeremias Maerki wrote:

I got another one. Probably a Xerces version problem. No good idea for
both problems, I'm afraid.
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or
change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(Unknown Source)
I guess you add an attribute with a QName prefix which isn't declared.
In DOM, the xmlns:prefix are indeed attributes and must be added
to the scope before createAttributeNS is called. I've been bitten
by this too, although I remember another wording of the error.
On 07.02.2004 23:56:40 J.Pietschmann wrote:
I get a nice Junit failure:
java.lang.LinkageError:
The JUnit FAQ explains this nicely.

J.Pietschmann



JUnit test failure

2004-02-07 Thread J.Pietschmann
Hi all,
I get a nice Junit failure:
Testcase: testFO2PDFWithDOM took 0.23 sec
Caused an ERROR
loader constraints violated when linking org/w3c/dom/Node class
java.lang.LinkageError: loader constraints violated when linking
 org/w3c/dom/Node class
 at org.apache.xalan.transformer.TransformerIdentityImpl.
  createResultContentHandler(TransformerIdentityImpl.java:186)
 at org.apache.xalan.transformer.TransformerIdentityImpl.
  transform(TransformerIdentityImpl.java:296)
 at org.apache.fop.BasicDriverTestCase.
  loadDocument(BasicDriverTestCase.java:133)
 at org.apache.fop.BasicDriverTestCase.
  testFO2PDFWithDOM(BasicDriverTestCase.java:149)
This seems to have something to do mixing Jars form the JDK and
fop/lib. Does anybody have an idea how this can be avoided?
J.Pietschmann