[jira] [Commented] (TUSCANY-3913) JCA otests fail when run with domain node

["Simon Laws (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081547#comment-13081547 ] 

Simon Laws commented on TUSCANY-3913:
-------------------------------------

The problem is that the domain node is not passing down the full set of contributions when resolving the composite and hence some of the configuration is incorrect. The following change fixes the problem for me however the just treats the symptom. I need to find out why the dependedOnContributions collection contains multiple copies of the same contribution. 

--- C:/Users/slaws/AppData/Local/Temp/DeployedComposite.java-revBASE.svn000.tmp.java	Tue Aug  9 10:43:30 2011
+++ C:/simon/svn/sca-java-2.x/modules/domain-node/src/main/java/org/apache/tuscany/sca/impl/DeployedComposite.java	Mon Aug  8 17:28:56 2011
@@ -92,6 +92,12 @@
         contributions.add(contribution);
         contributions.get(0).getDeployables().clear();
         contributions.get(0).getDeployables().add(composite);
+        
+        for (Contribution contribution : dependedOnContributions){
+            if (!contributions.contains(contribution)){
+                contributions.add(contribution);
+            }
+        }
 
         Map<QName, List<String>> bs = new HashMap<QName, List<String>>();
         if (endpointsIncludeDomainName) {

> JCA otests fail when run with domain node
> -----------------------------------------
>
>                 Key: TUSCANY-3913
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3913
>             Project: Tuscany
>          Issue Type: Bug
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0
>         Environment: all
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> I have a example RuntimeBridge which uses the domain node rather than the original node and with the new configuration the tests fail reporting that the SOAP intent cannot be resolved as the excluded intent of antiSOAP. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira