You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jason Pell (JIRA)" <ji...@apache.org> on 2013/02/06 09:29:13 UTC
[jira] [Updated] (CXF-4813) Java First @Policy at Operation level
has some issues with supporting some policy alternatives
[ https://issues.apache.org/jira/browse/CXF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4813:
----------------------------
Attachment: PolicySample.tar.gz
Maven project with 2 broken tests showing the issue.
> Java First @Policy at Operation level has some issues with supporting some policy alternatives
> ----------------------------------------------------------------------------------------------
>
> Key: CXF-4813
> URL: https://issues.apache.org/jira/browse/CXF-4813
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.7.3
> Reporter: Jason Pell
> Assignee: Jason Pell
> Attachments: PolicySample.tar.gz
>
>
> Policies with alternatives do not appear to be fully functional when applied at the Binding Operation level. They work perfectly when applied at the BINDING level (So when the @Policy is added at the SEI class level).
> I am attaching a test project which demonstrates the problem. This is probably a issue that can be worked around so its not a high priority.
> The only reason it became obvious was I wanted to be able to have no policy for operations such as Ping.
> Policies which do not have any alternative (so a single wsp:All instead of a wsp:ExactlyOne) work perfectly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira