[jira] [Issue Comment Edited] (TUSCANY-4014) Tidy up the binding model hierarchy

["Luciano Resende (Issue Comment Edited) (JIRA)" <de...@tuscany.apache.org>]

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

Luciano Resende edited comment on TUSCANY-4014 at 2/12/12 7:12 AM:
-------------------------------------------------------------------

It seems that we have the following :
BaseBindingImpl (located in core-spi) seems to be only used by LifecycleBinding in testing
BindingImpl (located in assembly) and used by CorbaBindingImpl, HazelcastBinding and HazelcastBinding

It seems safe to remove BaseBindingImpl, but before that, maybe update BindingImpl with some of it's model (e.g. unresolved and support for wireFormats and operationSelector models)

Another option is to get rid of both, and make the three bindings handle the binding model itself, as all other bindings are doing.
                
      was (Author: luciano resende):
    It seems that we have the following :
BaseBindingImpl (located in core-spi) and not really used by anyone
BindingImpl (located in assembly) and used by CorbaBindingImpl, HazelcastBinding and HazelcastBinding

It seems safe to remove BaseBindingImpl, but before that, maybe update BindingImpl with some of it's model (e.g. unresolved and support for wireFormats and operationSelector models)

Another option is to get rid of both, and make the three bindings handle the binding model itself, as all other bindings are doing.
                  
> Tidy up the binding model hierarchy
> -----------------------------------
>
>                 Key: TUSCANY-4014
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-4014
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0-Beta3
>         Environment: All
>            Reporter: Simon Laws
>            Priority: Minor
>             Fix For: Java-SCA-2.0
>
>
> As per TUSCANY-4013 the binding model is all over the pace in terms of what extends what. We seem to have two base implementations, BindingImpl and BaseBindingImpl, and very few binding models choose to extend them for some reason. Would be good to tidy this up. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira