You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2008/02/20 21:39:43 UTC
[jira] Resolved: (CXF-1411) WSPolicy alternatives are not selected
correctly on the server side
[ https://issues.apache.org/jira/browse/CXF-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1411.
------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
Patch applied
> WSPolicy alternatives are not selected correctly on the server side
> -------------------------------------------------------------------
>
> Key: CXF-1411
> URL: https://issues.apache.org/jira/browse/CXF-1411
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.1
> Reporter: Sergey Beryozkin
> Assignee: Daniel Kulp
> 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.