[
https://issues.apache.org/jira/browse/TUSCANY-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1762.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
The node implementation has been rewritten since this was reported so am
closing this issue.
> Intermittent failure of sample/implementation-composite build
> -------------------------------------------------------------
>
> Key: TUSCANY-1762
> URL: https://issues.apache.org/jira/browse/TUSCANY-1762
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.0
> Environment: All
> Reporter: Simon Laws
> Fix For: Java-SCA-1.1
>
>
> Sometimes I see
> -------------------------------------------------------
> Running composite.CompositeTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.296 sec <<<
> FAILURE!
> test(composite.CompositeTestCase) Time elapsed: 1.203 sec <<< ERROR!
> org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.contribution.service.ContributionResolveE
> xception: java.lang.ClassNotFoundException:
> org.apache.tuscany.sca.node.impl.NodeManagerServiceImpl
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
> at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance
> (SCADomain.java:58)
> Intermittently.
> Looking at this output it seems that the test is trying to load the
> node.composite from the node module and failing as it doesn't have the
> classes that that composite requires. It should actually be loading the
> composites under implementation-composite/src/main.resources.
> It's using the following to create the domain...
> scaDomain = SCADomain.newInstance();
> Which basically means it's going looking for
> sca-contribution.xml, sca-contribution-generated.xml (not sure this is the
> exact name) or deployables/ on the classpath
> In some circumstances it's finding the node version and in others it's
> finding the module version. I don't know what makes it do one or the other.
> The fix is the remove META-INF/sca-contribution from
> modules/node/src/main/resources.
> This is also the workround.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
