Some people are seeing....
-------------------------------------------------------
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.
There are two things we can do to try and fix this.
1/ in node, don't use the sca-contribution.xml for making the composite
deployable and remove the file so it can;t be found.
2/ make the implementation-composite sample use a more explicit constructor
identifying the local composite directly.
I'll have a go once past the current build problems.
Simon
