Configurable error handling when encountering unsupported assertions
--------------------------------------------------------------------

                 Key: CXF-796
                 URL: https://issues.apache.org/jira/browse/CXF-796
             Project: CXF
          Issue Type: Bug
            Reporter: Andrea Smyth


Currently, when the policy engine is enabled, an exception is thrown when it 
encounters an assertion for which no assertion builder is registered - either 
all of the assertions types must be understood or the policy engine must be 
disabled.
Change this to optionally only warn when encountering unknown assertion types, 
and also allow for the situation where an assertion is supported but no 
interceptor provider is registered for this  assertion.  This is helpful to 
digest wsdls with policy attachments that include proprietary assertion types 
such as {http://schemas.microsoft.com/net/2006/06/duplex}CompositeDuplex in 
http://131.107.72.15/ReliableMessaging_Service_WSAddressingAugust2004_Indigo/OneWay.svc?wsdl
As a workaround, it is easy enough to install trivial AssertionBuilder and 
PolicyInterceptorprovider implementations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to