With Kevin's great help, we found the culprit. It seems that the SAX2DOM
class from Xalan 2.7.0 cannot run with XercesImpl 2.8.0 with the following
exception:
java.lang.IncompatibleClassChangeError
at org.apache.xalan.xsltc.trax.SAX2DOM.startElement(SAX2DOM.java:140)
We tried to downgrade XercesImpl to 2.6.0 and it works!
Kevin, do you want to commit the fix for now? I'm thinking of removing the
Xalan dependency completely by copying the SAX2DOM utility into our code
base.
Thanks,
Raymond
----- Original Message -----
From: "Kevin Williams" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Thursday, July 27, 2006 9:39 AM
Subject: Re: Test case failures
Raymond was helping me with this yesterday. He noticed that if you run
the build from the respective subdirectory, the test succeeds. It seems
to only fail when the build is run from /java.
ant elder wrote:
I see the same failure with a fresh checkout of the code using the Sun
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Should I just commit a change to comment out the test for now?
...ant
On 7/26/06, Kevin Williams <[EMAIL PROTECTED]> wrote:
Yeah. I've tried those things and also just threw everything out and
tried to build from a fresh svn co. Same problem.
My verbose version info:
java>java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pwi32dev-20060511 (SR2))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
j9vmwi3223-2006050
4 (JIT enabled)
J9VM - 20060501_06428_lHdSMR
JIT - 20060428_1800_r8
GC - 20060501_AA)
JCL - 20060511a
--Kevin
Brent Daniel wrote:
> Kevin,
>
> For what it's worth, I'm using a somewhat older version of the IBM
> JDK than Raymond, and I'm also not seeing an error here when I do a
> full build on a fresh checkout. If indeed your build did succeed once,
> then it doesn't sound like a dependency issue. Maybe you're running
> into some sort of network hiccup in subsequent builds? Have you tried
> running offline? (mvn -o) Do you still see the failure if you do a
> full clean and rebuild?
>
>
> FYI, my "java -version":
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> pwi32dev-20051104)
>
> Brent
>
> On 7/25/06, Kevin Williams < [EMAIL PROTECTED]> wrote:
>
>> Hi Raymond,
>> I get the same error with your patched POM. I don't think my version
is
>> a beta release and I am also unsure of DocumentBuilderFactory
>> assumption.
>> --Kevin
>>
>>
>> Raymond Feng wrote:
>>
>> > Hi, Kevin.
>> >
>> > Is the Technology Edition a beta release? Can we assume the JDK 5.0
>> > always come with a DocumentBuilderFactory impl (I have never
checked
>> > the JSE 5.0 spec)?
>> >
>> > I have the following IBM JDK and it runs fine.
>> >
>> > java version "1.5.0"
>> > Java(TM) 2 Runtime Environment, Standard Edition (build
>> > pwi32dev-20060511 (SR2))
>> >
>> > Thanks,
>> > Raymond
>> >
>> > ----- Original Message ----- From: "Kevin Williams"
>> <[EMAIL PROTECTED]>
>> > To: < tuscany-dev@ws.apache.org>
>> > Sent: Monday, July 24, 2006 10:57 PM
>> > Subject: Re: Test case failures
>> >
>> >
>> >> Hi Raymond,
>> >>
>> >> I am using: IBM 32-bit SDK and Runtime Environment for Windows,
Java
>> >> 2 Technology Edition, Version 5.0
>> >>
>> >> I tried your patch but the result is a new failure:
>> >>
>> >> ======================================
>> >>
>> >> Downloading:
>> >>
http://repo1.maven.org/maven2/xerces/xerces/2.8.0/xerces-2.8.0.jar
>> >> [WARNING] Unable to get resource from repository central
>> >> (http://repo1.maven.or
>> >> /maven2)
>> >> [INFO]
>> >>
>> >>
>>
------------------------------------------------------------------------
>> >> [ERROR] BUILD ERROR
>> >> [INFO]
>> >>
>> >>
>>
------------------------------------------------------------------------
>> >> [INFO] Failed to resolve artifact.
>> >>
>> >> Missing:
>> >> ----------
>> >> 1) xerces:xerces:jar:2.8.0
>> >>
>> >> ===============================================
>> >>
>> >> There is no 2.8.0 direcrory under "xerces/xerces". I notice there
is
>> >> under "xerces/xercesImpl"
>> >>
>> >> --Kevin
>> >>
>> >>
>> >> Raymond Feng wrote:
>> >>
>> >>> Hi, Kevin.
>> >>>
>> >>> Which JDK do you use? It seems that it doesn't come with a DOM
>> >>> implementation.
>> >>>
>> >>> Can you try to apply the attched patch to
>> >>> databinding-framework/pom.xml?
>> >>>
>> >>> Thanks,
>> >>> Raymond
>> >>>
>> >>>
>> >>> ----- Original Message ----- From: "Kevin Williams"
>> >>> < [EMAIL PROTECTED]>
>> >>> To: <tuscany-dev@ws.apache.org>
>> >>> Sent: Monday, July 24, 2006 8:39 PM
>> >>> Subject: Test case failures
>> >>>
>> >>>
>> >>>> After having trouble getting svn update to succeed I reloaded
the
>> >>>> entire java tree. The first build attempt succeeded, I am
almost
>> >>>> certain :-), but subsequent attempts fail with this error:
>> >>>>
>> >>>>
>> >>>> [surefire] Running
>> >>>> org.apache.tuscany.databinding.impl.MediatorImplTestCase
>> >>>> [surefire] Tests run: 2, Failures: 0, Errors: 2, Time elapsed:
>> >>>> 0.041 sec
>> >>>> [surefire]
>> >>>> [surefire]
>> >>>>
>> testTransform1(org.apache.tuscany.databinding.impl.MediatorImplTestCa
>> >>>> se) Time elapsed: 0.031 sec <<< ERROR!
>> >>>> javax.xml.parsers.FactoryConfigurationError: Provider for
>> >>>> javax.xml.parsers.Docu
>> >>>> mentBuilderFactory cannot be found
>> >>>> at
>> >>>> javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown
>> Source)
>> >>>> at
>> org.apache.xalan.xsltc.trax.SAX2DOM.<init>(SAX2DOM.java :57)
>> >>>> at
>> >>>>
>> org.apache.tuscany.databinding.xml.SAX2DOMPipe.<init>(SAX2DOMPipe.jav
>> >>>> a:35)
>> >>>> at
>> >>>>
>> org.apache.tuscany.databinding.impl.MediatorImplTestCase.setUp(Mediat
>> >>>> orImplTestCase.java:61)
>> >>>> at junit.framework.TestCase.runBare (TestCase.java:125)
>> >>>> at junit.framework.TestResult$1.protect(TestResult.java
:106)
>> >>>> at
>> junit.framework.TestResult.runProtected(TestResult.java :124)
>> >>>> at junit.framework.TestResult.run(TestResult.java:109)
>> >>>> at junit.framework.TestCase.run(TestCase.java:118)
>> >>>> at junit.framework.TestSuite.runTest(TestSuite.java:208)
>> >>>> at junit.framework.TestSuite.run(TestSuite.java:203)
>> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native
>> Method)
>> >>>> at
>> >>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>>> java:64)
>> >>>> at
>> >>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >>>> sorImpl.java:43)
>> >>>> at java.lang.reflect.Method.invoke (Method.java:615)
>> >>>> at
>> >>>>
>> org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBatt
>> >>>> ery.java:242)
>> >>>> at
>> >>>>
>> org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.j
>> >>>> ava:216)
>> >>>> at
>> >>>>
>> org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
>> >>>> at org.apache.maven.surefire.Surefire.run(Surefire.java
:163)
>> >>>> at org.apache.maven.surefire.Surefire.run (Surefire.java
:87)
>> >>>> at
org.apache.maven.surefire.Surefire.run(Surefire.java:63)
>> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> >>>> at
>> >>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>>> java:64)
>> >>>> at
>> >>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >>>> sorImpl.java:43)
>> >>>> at java.lang.reflect.Method.invoke (Method.java:615)
>> >>>> at
>> >>>>
>> org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:785
>> >>>> )
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >>>> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>>>
>> >>> Index: pom.xml
>> >>>
===================================================================
>> >>> --- pom.xml (revision 425233)
>> >>> +++ pom.xml (working copy)
>> >>> @@ -47,6 +47,12 @@
>> >>> <scope>compile</scope>
>> >>> </dependency>
>> >>> <dependency>
>> >>> + <groupId>xerces</groupId>
>> >>> + <artifactId>xerces</artifactId>
>> >>> + <version> 2.8.0</version>
>> >>> + <scope>test</scope>
>> >>> + </dependency>
>> >>> + <dependency>
>> >>> <groupId>junit</groupId>
>> >>> <artifactId>junit</artifactId>
>> >>> </dependency>
>> >>>
>> >>>
>>
------------------------------------------------------------------------
>> >>>
>> >>>
>> >>>
>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >>> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>>
>> >>
>> >>
>> >>
>> >>
---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >
>> >
>> >
---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> >
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
