cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions
Date Wed, 21 Sep 2011 10:38:09 GMT

    [ https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109400#comment-13109400
] 

Sergey Beryozkin commented on CXF-3816:
---------------------------------------

Hi Aki
IMHO that would go against the policy spec. If the policy is coming back to the client then
it just has to be understood. I'd consider using the existing ignoreUnknownAssertions for
ignoring what is known to be a really optional policy which just has not been declared properly
in WSDL, i.e, as if it is strictly required to be understood. I'd recommend:
- keep ignoreUnknownAssertions and use only for 'fixing' policy declaration bugs - both at
the bootstrap & runtime time
- fix the CXF client policy code and late-throw exceptions only when no alternative has been
found

but add this new property only if the code changes are really tricky :-) 

> 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

        

Mime
View raw message