You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2009/02/26 12:35:01 UTC
[jira] Resolved: (TUSCANY-2879) [1.x] ITest failure in
TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws resolved TUSCANY-2879.
---------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-Next
I'm getting a clean build now in 1.x
> [1.x] ITest failure in TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase
> ------------------------------------------------------------------------------
>
> Key: TUSCANY-2879
> URL: https://issues.apache.org/jira/browse/TUSCANY-2879
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: branch 1.x revision 747826
> Reporter: Dan Becker
> Fix For: Java-SCA-Next
>
>
> <testcase time="0.094" name="testCalculator">
> <failure message="null expected:&lt;[InvalidWSDLInterfaceAttr]&gt;
> but was:&lt;[AttributeCannotBeProcessed]&gt;"
> type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: null expected:&lt;[InvalidWSDLInterfaceAttr]&gt; but was:&lt;[AttributeCannotBeProcessed]&gt;
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at junit.framework.Assert.assertEquals(Assert.java:87)
> at interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase.testCalculator(InvalidWSDLInterfaceAttrTestCase.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> </failure>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.