[
https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109859#comment-13109859
]
Sergey Beryozkin commented on CXF-3816:
---------------------------------------
Hi Dan, Aki, sure, totally agreed re the motivation behind introducing the
interceptor.
may be I've misunderstood it a bit. I was just saying that
ignoreUnknownAssertions seems like the property
which can handle this issue - at the bootstrap time at least. But of course the
issue then which unknown policies which were
ignored at bootstrap can be ignored at the runtime - I think I'm getting it
:-). Good idea...
> A policy provider/interceptor for ignoring (i.e., automatically asserting)
> specified policy assertions
> ------------------------------------------------------------------------------------------------------
>
> Key: CXF-3816
> URL: https://issues.apache.org/jira/browse/CXF-3816
> Project: CXF
> Issue Type: New Feature
> Components: WS-* Components
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Priority: Minor
> Fix For: 2.5
>
>
> Introduce an option to ignore, in other words, to automatically assert a set
> of policy assertions.
> When a WSDL contains unknown policy assertions, the current
> "ignoreUnknownAssertion" property is used to ignore those unknown policy
> assertions during the assertion building, but not during the verification of
> the assertions.
> We introduce a new policy provider IgnorablePolicyProvider that can be
> configured to register a set of assertion names that can be ignored (i.e.,
> automatically asserted) later during the processing.
> The background is discussed in the following mail thread:
> http://cxf.547215.n5.nabble.com/doubt-on-ignoreUnknownAssertions-option-in-ws-policy-tt4823222.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
