[
https://issues.apache.org/jira/browse/CXF-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-4073.
------------------------------
Resolution: Fixed
I had to fix a bunch of things with the patch, but it's now applied.
1) Checkstyle issues all over the place.
2) Use of a HashSet instead of a concurrent form. Likely not a big deal, but
better to be safe.
3) Updates to the ws-rm module to take the new api into account.
4) The result was still a failing test due to the change from returning null to
an empty list causing a different policy alternative to be selected.
In anycase, things are updated now.
> Support multiple policy interceptor providers per policy assertion
> ------------------------------------------------------------------
>
> Key: CXF-4073
> URL: https://issues.apache.org/jira/browse/CXF-4073
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Reporter: Andrei Shakirin
> Assignee: Daniel Kulp
> Fix For: 2.6
>
> Attachments: cxf-rt-ws-policy.patch
>
>
> Hi,
> At the moment policy mechanism is very powerfull, but have some limitation.
> One of them is that it is possible to register only one InterceptorProvider
> for one policy assertion.
> PolicyInterceptorProviderRegistry interface extends Regsitry as:
> public interface PolicyInterceptorProviderRegistry
> extends Registry<QName, PolicyInterceptorProvider> {
> I see some use cases where PolicyInterceptorProvider(s) are independent, but
> associated with the same policy assertion (for example in complex
> authentication case).
> Proposal: extend PolicyInterceptorProviderRegistry to save set of
> PolicyInterceptorProvider for one assertion.
> If proposal is accepted I will provide patch.
> Regards,
> Andrei.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
