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

["Vamsavardhana Reddy (JIRA)" <tu...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsavardhana Reddy updated TUSCANY-2296:
-----------------------------------------

    Attachment: TUSCANY-2296-recreate.patch

TUSCANY-2296-recreate.patch: Helps better understand the problem I am facing.

> 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.