You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tuscany.apache.org by "Simon Nash (JIRA)" <de...@tuscany.apache.org> on 2008/07/02 10:02:47 UTC

[jira] Resolved: (TUSCANY-2449) Binding builders for component and composite services should be separated

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

Simon Nash resolved TUSCANY-2449.
---------------------------------

    Resolution: Fixed

Fixed in the 1.3 branch under r673307 and in trunk under r673310.

The naming convention for these builders now more accurately reflects their purpose:

   ComponentServiceBindingBuilder does the binding building for component services within a composite.  (This was previously done as the first part of CompositeServiceBindingBuilder.)

   CompositeServiceBindingBuilder does the binding building for composite services within a composite.  (This was previously done as the second part of CompositeServiceBindingBuilder.)

   ComponentReferenceBindingBuilder does the binding building for component references within a composite.  (This was previously called CompositeReferenceBindingBuilder.)


> Binding builders for component and composite services should be separated
> -------------------------------------------------------------------------
>
>                 Key: TUSCANY-2449
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2449
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-1.3
>         Environment: All
>            Reporter: Simon Nash
>            Assignee: Simon Nash
>             Fix For: Java-SCA-1.3
>
>
> The binding builders for component services and composite services are currently combined into a single builder.  These should be separated into two separate builders.  This would provide flexibility to run these builders at different stages of the builder sequence if necessary, or to run them in a different order, or possibly to omit one of them in some cases.  This is not possibly with the current code structure, which requires that they are always run together with the component services builder being run first.

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