[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-bindings] ISSUE-48: How are mayProvide intents on bindingssatisfied
Logged as: http://www.osoa.org/jira/browse/BINDINGS-48 -Eric. ashok malhotra wrote: > The SCA Policy spec says that in addition to the intents that a > bindingType alwaysProvides > > "... The binding type also declares the intents that it may provide by > using the optional @mayProvide attribute. Intents listed as the value > of this attribute can be provided by a binding instance configured > from this binding type." > > > My assumption was that, to use some of the mayProvide intents, a > binding instance had to be configured outside of SCA and then that > instance used for some service/reference. At last week's Policy f2f, > it became clear that this assumption was not universally shared. Some > thought that the SCA runtime would configure the binding instance > during the deployment phase. > > > I looked at the binding.ws, the binding.jca and the binding.jms specs > and found that, as expected, binding.ws says nothing about mayProvide. > Binding.jca does not say anything about mayProvides either. > Binding.jms says > > > <bindingType type=”binding.jms” > alwaysProvides=”jms” mayProvide=”atLeastOnce atMostOnce ordered > conversational”/> > > > but it does not say how the mayProvides intents are satisfied. That > is, it does not say what configuration parameters can used to provide > these intents. > > > Thus, two requests > > > - Clarify whether the binding instances configured to provide the > capabilities indicated in mayProvides are generated separately, > earlier and outside of SCA and then used in the SCDL or whether they > are generated by the SCA runtime. > > > - As far as possible, indicate in the bindings specs which > configuration parameters need to be tweaked and how to satisfy the > mayProvide intents. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]