OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE-61: How are mayProvide intents on bindings satisfied


http://www.osoa.org/jira/browse/POLICY-61

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Inactive hide details for ashok malhotra ---10/07/2008 12:17:41 PM---The SCA Policy spec says that in addition to the intents tashok malhotra ---10/07/2008 12:17:41 PM---The SCA Policy spec says that in addition to the intents that a bindingType alwaysProvides


From:

ashok malhotra <ashok.malhotra@oracle.com>

To:

OASIS Policy <sca-policy@lists.oasis-open.org>, OASIS Bindings <sca-bindings@lists.oasis-open.org>

Date:

10/07/2008 12:17 PM

Subject:

[sca-policy] NEW ISSUE: How are mayProvide intents on bindings satisfied





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.


--
All the best, Ashok

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]