This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6721 - All: Attaching policy to implicit operations
Summary: All: Attaching policy to implicit operations
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: All (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
Depends on: 6402 6403 6406 6694
Blocks: 6463
  Show dependency treegraph
Reported: 2009-03-19 18:24 UTC by Katy Warr
Modified: 2015-06-20 16:35 UTC (History)
1 user (show)

See Also:

implicit ops (189.00 KB, application/msword)
2009-10-02 08:42 UTC, Doug Davis
implicit (189.50 KB, application/msword)
2009-10-02 10:06 UTC, Doug Davis
latest (190.00 KB, application/msword)
2009-10-02 10:18 UTC, Doug Davis

Description Katy Warr 2009-03-19 18:24:25 UTC
There are a number of issues already open addressing how we attach policies to indicate that an endpoint supports virtual (implicit) operations and the flavour/extent of that support.  For example,issue 6403 describes policy to indicate that an endpoint supports enumeration and there are similar issues open for the other specs (6402,6406, 6407).

These issues do not discuss how policy should be attached to the virtual operation (i.e. one that does not appear in WSDL) itself.  They also don't address what policy should be applied to the virtual operations by default.  One option for default behaviour might be to default to the policy of the endpoint, but this poses problems as many policies are applied at operation/message level (and therefore are not available at the endpoint).

There are a number of possible solutions that we might adopt to solve this problem.  I suggest that we choose a pattern and re-use that across all the specs for simplicity and consistency.

For example, here's a potential pattern:

   ... <lots of policy for the endpoint>

   <wsra policy indicating wsra spec support>


   </wsra policy indicating wsra spec support>


The VirtualOperationPolicy defines the policy for the implicit operations relating to the wsra spec support.

For example, the above pattern applied to eventing MIGHT look something like this:

<wsev:WSEventingSupported  ...>
        ... policies such as security policy to attach to subscribe request ...


If we agree on a pattern to try, the next step might be to take some real examples (e.g. security policy) in order to check that the pattern works prior to applying it across the specs.

This issue is also related to which asks when operations do/don't appear in the WSDL.  

It's probably best for us to address the other policy issues and 6694 before this one - but this is an important issue as lack of clear specification in this area will prevent interoperability and make life hard for implementers.
Comment 4 Doug Davis 2009-10-02 08:42:44 UTC
Created attachment 761 [details]
implicit ops
Comment 5 Doug Davis 2009-10-02 10:06:14 UTC
Created attachment 767 [details]
Comment 6 Doug Davis 2009-10-02 10:18:03 UTC
Created attachment 768 [details]
Comment 7 Robert Freund 2009-10-02 10:19:55 UTC
resolved with comment #6
Comment 8 Jackie 2015-06-20 16:34:34 UTC
Please make my changes
Comment 9 Jackie 2015-06-20 16:35:23 UTC
Please make my changes