sca-bindings message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Comments on proposed resolution to BINDINGS-126
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: sca-bindings@lists.oasis-open.org
- Date: Fri, 9 Apr 2010 11:00:13 +0100
Mike,
Here's my comments on the proposal that's
in JIRA:
> A binding.ws implementation
MUST support the WS-Policy specification and MUST:
"MUST support the WS-Policy specification"
seems a bit vague to me - isn't that what the following list defines in
more detail?
Also, I don't think we've used "binding.ws
implementation" anywhere in normative statements, to be consistent
this would be "SCA runtime"
> a) accept WS-Policy statement
in any supplied WSDLs
Basically I believe what we are saying
here is that an SCA runtime MUST not reject a WSDL simply because it includes
WS-Policy statements, which is perhaps somewhat different to "accept"ing
WS-Policy statements.
> b) advertise any policies
applied to a service using the WS-Policy language
Would the default WSDL generation rules
be impacted by this? Are we saying that all policies that are applied
to be a service MUST be represented as WS-Policy statements in the WSDL,
or are we saying that IF there are any policy statements in the WSDL, they
must at least be expressed using WS-Policy? I'm not sure how we could
check that any WSDL extensibility elements present in other namespaces
are policy-related rather than anything else.
> c) accept WS-Policy statements
in SCA policySets
As above
> d) use the WS-Policy policy
intersection rules when matching policies between a reference and a service
[BWS20038]
I think more discussion is needed around
what happens with the combination of WS-Policy statements in the WSDL referred
to by a binding.ws and the SCA policy sets. From the Web Service
binding spec:
"If the binding is for an SCA reference,
the set of available ports for the reference consists of the ports in the
WSDL service that have portTypes which are compatible supersets of the
SCA reference as defined in the SCA Assembly Model specification [SCA-Assembly]
and satisfy all the policy constraints of the binding."
Does this issue affect the definition
of the "set of available ports"? Would they need to satisfy
all the policy constraints of the binding as well as all the policy constraints
described in the WSDL?
Regards, Simon
Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair,
AT&T and Boeing Lab Advocate
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]