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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

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


Subject: Re: [sca-bindings] [BINDINGS-126] binding.ws should REQUIRE supportfor WS-Policy


Logged as: http://www.osoa.org/jira/browse/BINDINGS-126

-Eric.

On 04/08/2010 04:01 AM, Mike Edwards wrote:
OFDED14A78.620190E2-ON802576FF.003AAC61-802576FF.003C962F@uk.ibm.com" type="cite">Description:

The current binding.ws specification makes no normative statements which relate to WS-Policy.

However, there are clearly parts of the specification that do relate to WS-Policy and it also the case that
for Web services, WS-Policy is the defined policy language.

I believe that the binding.ws specification should make a definite statement about support for WS-Policy
as a policy language.

Note that this does not imply a requirement for the support of any specific concrete policies that might be
expressed in the WS-Policy language.  It does imply that a binding.ws implementation cannot fail merely
because it encounters WS-Policy constructs.  It also implies that IF a binding.ws instance seeks to advertise
policies then it must do so using WS-Policy.

Proposal:

Add a normative statement that a binding.ws implementation must support the WS-Policy specification:

This support takes the following forms:

a) accepting WS-Policy statements in supplied WSDLs
b) advertising applied policies in generated WSDLs
c) accepting WS-Policy statements in PolicySets
d) for the purposes of policy matching between references and services, the binding.ws implementation
must follow the policy intersection rules of WS-Policy

The support DOES NOT imply that a binding.ws implementation must support any particular concrete policy
expressed using WS-Policy.

Detailed text:

Add a new section 2.10, as follows:

2.10 Support for WS-Policy specification

A binding.ws implementation MUST support the WS-Policy specification and MUST:
a) accept WS-Policy statement in any supplied WSDLs
b) advertise any policies applied to a service using the WS-Policy language
c) accept WS-Policy statements in SCA policySets
d) use the WS-Policy policy intersection rules when matching policies between a reference and a service
[BWS20038]

Note that the requirements relating to WS-Policy do not mandate that the binding.ws implementation has to
support any specific concrete policies.  The requirements are that the WS-Policy language itself must be
supported and that the presence of WS-Policy constructs cannot be used to reject an SCA artifact.
 


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