[jira] Assigned: (TUSCANY-3425) Look into reworking autowire matching to rely on build time endpoint registry matching

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

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

Simon Laws reassigned TUSCANY-3425:
-----------------------------------

    Assignee: Simon Laws

> Look into reworking autowire matching to rely on build time endpoint registry matching
> --------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3425
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3425
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0-M4
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>
> The last vestige of build time/non-registry based matching looks for autowire candidates across the local composite. I'm in two minds about how to rationalize this. I have an AUTOWIRE_CANDIDATE status that allows an endpoint reference to be passed into the binder where there autowire code can then runt and look in the registry. This does however mean enabling the build time matching code that is sitting the NodeFactoryImpl. Needs a bit more thinking. 

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