You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Ramkumar Ramalingam (JIRA)" <de...@tuscany.apache.org> on 2008/08/06 16:38:44 UTC
[jira] Commented: (TUSCANY-2532) Test case failure in
itest/validation DoesntProcessHeadersTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620268#action_12620268 ]
Ramkumar Ramalingam commented on TUSCANY-2532:
----------------------------------------------
Hi Simon,
Looking at the recent JMSBindingProcessor.java code, I could figure out that this testcase is no more valid as we now process the "headers" in binding.jms. This was not the case earlier..... here is how the method looked like earlier
private void parseHeaders(XMLStreamReader reader, JMSBinding jmsBinding) throws XMLStreamException {
warning("DoesntProcessHeaders", jmsBinding);
}
Now, this method is been changed to handle the hearders tag, hence we can't see this warning anymore.
I will use this JIRA, TUSCANY-2532 to remove this testcase and add new ones as per the latest changes.
> Test case failure in itest/validation DoesntProcessHeadersTestCase
> ------------------------------------------------------------------
>
> Key: TUSCANY-2532
> URL: https://issues.apache.org/jira/browse/TUSCANY-2532
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: Windows
> Reporter: Simon Nash
> Assignee: Ramkumar Ramalingam
> Priority: Blocker
> Fix For: Java-SCA-Next
>
>
> On revision level r682511, I get the following failure building itest/validation. There's a test case update in r682633 that bypasses the failure, but it seems that this is concealing the true problem, which is that the correct diagnostic is not being produced.
> The actual diagnostic being produced is NoCompositeNamespace. The diagnostic that should be produced is DoesntProcessHeaders.
> The cause of the NoCompositeNamespace error should be investigated and resolved. From the build log, it appears that this is caused by the warning "WARNING: No namespace found: Composite = RPCComposite". When this problem has been resolved, we will be able to see whether the correct DoesntProcessHeaders diagnostic is produced.
> Here's the build log for the failure:
> Running binding.jms.DoesntProcessHeadersTestCase
> 05-Aug-2008 15:21:45 org.apache.tuscany.sca.contribution.resource.impl.ResourceI
> mportProcessor
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.114 sec <<< FA
> ILURE!
> SEVERE: Attribute 'uri' is missing
> testCalculator(binding.jms.DoesntProcessHeadersTestCase) Time elapsed: 0.059 se
> c <<< FAILURE!
> 05-Aug-2008 15:21:45 org.apache.tuscany.sca.workspace.builder.impl.ContributionD
> ependencyBuilderImpl
> junit.framework.ComparisonFailure: null expected:<[DoesntProcessHeaders]> but wa
> s:<[NoCompositeNamespace]>
> WARNING: Unresolved import: Import = null
> at junit.framework.Assert.assertEquals(Assert.java:81)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.assembly.xml.CompositeProcessor
> at junit.framework.Assert.assertEquals(Assert.java:87)
> WARNING: No namespace found: Composite = RPCComposite
> at binding.jms.DoesntProcessHeadersTestCase.testCalculator(DoesntProcess
> HeadersTestCase.java:58)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.node.impl.NodeImpl <init>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO: Creating node: file:/F:/tuscany78/sca/itest/validation/src/main/resources/
> UnresolvedComponentImplementation/Calculator.composite
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.node.impl.NodeImpl configureNode
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> INFO: Loading contribution: file:/F:/tuscany78/sca/itest/validation/src/main/res
> ources/UnresolvedComponentImplementation/
> at java.lang.reflect.Method.invoke(Method.java:585)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.node.impl.NodeImpl configureNode
> at junit.framework.TestCase.runTest(TestCase.java:168)
> INFO: Loading composite: file:/F:/tuscany78/sca/itest/validation/src/main/resour
> ces/UnresolvedComponentImplementation/Calculator.composite
> at junit.framework.TestCase.runBare(TestCase.java:134)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.assembly.builder.impl.ComponentConfi
> gurationBuilderImpl
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> WARNING: Component implementation not found: Component = AddServiceComponent_one
> Uri = null
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.assembly.builder.impl.CompositeBindi
> ngURIBuilderImpl
> WARNING: Component implementation not found: Component = AddServiceComponent_one
> Uri = null
> at junit.framework.TestCase.run(TestCase.java:124)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.policy.xml.BindingTypeProcessor
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> SEVERE: Required attribute type missing from BindingType Definition
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.
> java:35)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.implementation.java.introspect.impl.
> JavaIntrospectionHelper checkInvalidAnnotations
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.
> java:62)
> WARNING: Invalid annotation @org.osoa.sca.annotations.Reference(required=true, n
> ame=) is found on private void impl.java.CalculatorServiceImpl.add(int,int)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes
> tSet(AbstractDirectoryTestSuite.java:138)
> 05-Aug-2008 15:21:46 org.apache.tuscany.sca.implementation.java.xml.JavaImplemen
> tationProcessor
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab
> stractDirectoryTestSuite.java:125)
> SEVERE: Contribution Resolve Exception occured due to:
> 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(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su
> refireBooter.java:308)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j
> ava:879)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.