[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: Rules for Binding compatibility
TARGET: All binding specs DESCRIPTION: This issue is derived from a concern raised by the SCA Policy TC (SPTC). The only SCA spec which mentions binding compatibility is the Policy FW spec. The SPTC believes that policy compatibility is a required element of binding compatibility, but the SPTC does not believe that it should be the only means for determining compatibility. Further, the SPTC believes that the current binding compatibility rule (in the Policy FW spec) of strict bindingType matching is overly constraining. For example, suppose there existed <binding.axis1/> and <binding.axis2/>. These two bindings might be interoperable/compatible. If this is a desirable use case to support, then how would a wire validator know this? The referenced JIRA below mentions binding hierarchy, but that would be one of several possible solutions. The SPTC is not recommending a solution. The SPTC believes that defining binding compatibility belongs with the SCA Binding TC and/or the SCA Assembly TC. Policy Issue 14: http://www.osoa.org/jira/browse/POLICY-14 is the root of the discussion. I mention it here because this is the issue under which the SPTC is tracking the concern. The contents of the JIRA itself are potentially misleading. PROPOSAL: none Dave Booz STSM, SCA and WebSphere Architecture Co-Chair OASIS SCA-Policy TC "Distributed objects first, then world hunger" Poughkeepsie, NY (845)-435-6093 or 8-295-6093 e-mail:booz@us.ibm.com http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]