cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] Commented: (CXF-2003) Failure in unit test AnnotatedTypeTest.testAegisType
Date Sun, 25 Jan 2009 10:11:59 GMT


Christian Schneider commented on CXF-2003:

I have found the reason for the failed tests. Seems the problem is in DOMUtils.getChildrenWithName.
It tries to compare a namespace of "" with a namespace of null. 

I will commit a small patch that should solve the problem. Could someone please review if
the fix is done right?

After this patch I get only the following unit test results:
Tests in error:

Tests run: 148, Failures: 0, Errors: 9, Skipped: 3

> Failure in unit test AnnotatedTypeTest.testAegisType
> ----------------------------------------------------
>                 Key: CXF-2003
>                 URL:
>             Project: CXF
>          Issue Type: Test
>          Components: Aegis Databinding
>    Affects Versions: 2.1.3
>         Environment: Windows Vista
> JDK 1.6.0 update 10
>            Reporter: Christian Schneider
> Currently the test AnnotatedTypeTest.testAegisType fails for me with the following log:
> org.junit.ComparisonFailure: expected:<att[Prop]> but was:<att[ributeProperty]>
> 	at org.junit.Assert.assertEquals(
> 	at org.junit.Assert.assertEquals(
> 	at org.apache.cxf.aegis.type.java5.AnnotatedTypeTest.testAegisType(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.junit.internal.runners.TestMethod.invoke(
> 	at org.junit.internal.runners.MethodRoadie.runTestMethod(
> 	at org.junit.internal.runners.MethodRoadie$
> 	at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(
> 	at org.junit.internal.runners.MethodRoadie.runTest(
> 	at
> 	at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(
> 	at org.junit.internal.runners.JUnit4ClassRunner.runMethods(
> 	at org.junit.internal.runners.JUnit4ClassRunner$
> 	at org.junit.internal.runners.ClassRoadie.runUnprotected(
> 	at org.junit.internal.runners.ClassRoadie.runProtected(
> 	at
> 	at
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
> When looking at the code of AnnotatedBean3 the attribute seems to be named attributeProperty.
So there is no wonder that the failure happens.
> If I understand this correctly the code of the test should be changed to expect "attributeProperty".
>         assertEquals("attributeProperty", q.getLocalPart());
> What I donĀ“t understand is that this problem does not show in the continuous integration
builds. Or does it show?
> That is why I hesitated to commit the change myself.
> Could someone with access to the continuous integration system check if the failure also
happens there and if it is safe to do the above change.
> I have several other unit test failures that I will report once I understand this issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message