[jira] Commented: (TUSCANY-2296) SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed

["ant elder (JIRA)" <tu...@ws.apache.org>]

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

ant elder commented on TUSCANY-2296:
------------------------------------

I'm thinking about closing this as Working-As-Designed, but I'll just say this now and leave the JIRA open for a while to see if there are other comments.

It does work as you've described and I agree that can seem unintuitive, but thats the way org.apache.tuscany.host.embedded.SCADomain works - the entire thing is treated as a contribution and all composites in that contribution get processed, the composite passed in on the newInstance call is the _deployable_ composite not  the sole composite to be processed. 

There is a SCADomain newInstance method that takes both a contribution location and  list of deployable composites and I think there IS a bug in that which means the contribution location often gets ignored, but really to clean all this up properly requires sorting out what to do with all the new domain/node/node2 etc stuff.  


   

> SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2296
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2296
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Embedded Runtime
>    Affects Versions: Java-SCA-1.2
>            Reporter: Vamsavardhana Reddy
>             Fix For: Java-SCA-Next
>
>         Attachments: TUSCANY-2296-recreate.patch
>
>
> I have two composites, namely "proper.composite" and "error.composite", in my test project.  "proper.composite" is used to test proper contribution without any errors whereas "error.composite" is used to test a problematic contribution.  But when I initialize a domain using SCADomain. newInstance("proper.composite"), I am getting an exception due to "error.composite".  Though it looks as if the call SCADomain. newInstance("proper.composite") processes only "proper.composite", in reality it is processing all the .composite files present in the project irrespective of the parameter passed to SCADomain.newInstance().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.