cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] Updated: (CXF-1411) WSPolicy alternatives are not selected correctly on the server side
Date Mon, 18 Feb 2008 11:38:36 GMT


Sergey Beryozkin updated CXF-1411:

    Attachment: cxf-pacth-1411.patch

1. PolicyAssertion interface introduced, extends Assertion
2. Policy instances are asked now to check if they've been asserted
3. PolicyInterceptorProvider has new methods whic can be used to retrieve interceptors lazily,
on demand
4. A given server endpoint has all the assertions in all the alternatives added to it. This
can be optimized further once we have the on-demand provisioning of interceptors
5. Updated WSA MAPAggregator to better assert Anonymous and NonAnonymous nested assertions
6. Added a new Addressing system test veifying that  Anonymous requests can be asserted.

> WSPolicy alternatives are not selected correctly on the server side
> -------------------------------------------------------------------
>                 Key: CXF-1411
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.1
>            Reporter: Sergey Beryozkin
>             Fix For: 2.1
>         Attachments: cxf-pacth-1411.patch
> One can use WS-Policy to describe multiple policy alternatives :
> <Policy>
>   <!-- alt1 -->
>   <All>
>       <A/>
>   </All>
>   <!-- alt2 -->
>   <All>
>       <B/>
>   </All>
>   <!-- alt3 -->
>    <All>
>        <A/>
>        <B/>
>     </All>
> </Policy>
> The main motivation behind using multiple alternatives is to let policy-aware clients
to select only that alternative which they understand. Thus a service may be consumed by clients
which understand <A/> only and by clients which understand <B/> only and by those
which understand both A&B.
> As such, a server needs to be aware of all the assertions (A, B) available in Multiple
alternatives to satisfr requests from different types of clients.
> Currently, server selects only a single alternative. For example, by selecting Alt1 (A
only) it will reject valid requests meeting B or A&B requirements

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message