ISSUE 7: Replacement of binding types

["Martin Chapman" <martin.chapman@oracle.com>]

Logged: http://www.osoa.org/jira/browse/ASSEMBLY-7

>-----Original Message-----
>From: Peshev, Peter [mailto:peter.peshev@sap.com] 
>Sent: Friday, October 05, 2007 3:27 PM
>To: sca-assembly@lists.oasis-open.org
>Subject: [sca-assembly] NEW ISSUE: Replacement of binding types
>
>
>TARGET: SCA Assembly Specification
>
>DESCRIPTION: Each binding defined in the SCA specification 
>should have a bindingType. 
>For example the current bindingType of the binding.jms is defined as :
>
><bindingType type="binding.jms" alwaysProvides="jms" 
>mayProvide="atLeastOnce atMostOnce ordered conversation"/>
>
>Some vendors support more features that are not part of the 
>standard on which the binding is based so it should be 
>mentioned how it is possible to extend the existing specs. For 
>wexample whether the standard bindingType that is defined 
>within a binding spec, could be replaced (by adding supported 
>intents) or the recommended solution is to define an extension 
>for the whole binding -- i.e.  binding.sap.jms.
>
>
>PROPOSAL: Provide functionality and sample for such extension.
>