You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2011/09/21 12:28:08 UTC

[jira] [Created] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

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

        

[jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109819#comment-13109819 ] 

Daniel Kulp commented on CXF-3816:
----------------------------------


Sergey, this topic came up last week in regards to the NTLM policy that MS likes to stick into the WSDL.   We CAN support NTLM via some configuration and such.  Thus, if the user is careful, the client could easily meet all the requirements of the policy.   However, because of that assertion in the WSDL, the client won't work.   Having an easy way to say "OK, I'm aware of this policy and I'm handling it manually" is a good thing.

Without that, they would need to write a Neethi AssertionBuilder  (relatively easy, subclass the neethi PrimitiveAsertionBuilder probably) as well as a PolicyInterceptorProvider and an Interceptor to assert the policy.   A bit complicated.    What Aki wants to do is provide all of the above in a simple to use bean.

That said, for the case of NTLM, a submission of a full set of policy handlers that would handle the configuration and validation of NTLM would definitely be appreciated.  :-)





> 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

        

[jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112608#comment-13112608 ] 

Aki Yoshida commented on CXF-3816:
----------------------------------

Hi Dan, Sergey,
thanks for your comments.

I introduced a policy provider that can be configured to assert specified policy assertions. I hope this will be useful in those scenarios that need to consume some legacy WSDLs or proprietary ones.

regards, aki

> 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

        

[jira] [Resolved] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aki Yoshida resolved CXF-3816.
------------------------------

    Resolution: Fixed

> 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

        

[jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109429#comment-13109429 ] 

Aki Yoshida commented on CXF-3816:
----------------------------------

Hi Sergey,

I thought introducing a special policy provider would be another way of "understanding" the policy, assuming you somehow handled the requirements of those explicitly excluded policy assertions using other means.

If we don't provide such a convenience policy provider, I think the users will be writing their own any way to workaround this practical problem. So, I thought it would be practical to have one available out of the box to use, no?

regards, aki

> 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

        

[jira] [Commented] (CXF-3816) A policy provider/interceptor for ignoring (i.e., automatically asserting) specified policy assertions

Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
    [ 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