[jira] Commented: (CXF-2518) UltimateReceiverMustUnderstandInterceptor in wrong phase?

["Daniel Kulp (JIRA)" <ji...@apache.org>]

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

Daniel Kulp commented on CXF-2518:
----------------------------------

This is working as designed.   With 2.2, the service itself has the option of processing the header list and removing the stuff it knows about.   Thus, we need to do the checking AFTER the invoke.   

With 2.3, this is changing.   The service will need to configure ahead of time (properties) what headers it will be responsible for.  With that knowledge, we can fault out sooner.


> UltimateReceiverMustUnderstandInterceptor in wrong phase?
> ---------------------------------------------------------
>
>                 Key: CXF-2518
>                 URL: https://issues.apache.org/jira/browse/CXF-2518
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>         Environment:   	
> « Hide
> System:
> 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux
> Java:
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
> Apache CXF 2.2.3 (not in version list)
>            Reporter: Christian Connert
>
> Hi,
> The MustUnderstandInterceptor adds the UltimateReceiverMustUnderstandInterceptor if some headers without a role are part of the soap header.
> The problem is that the UltimateReceiverMustUnderstandInterceptor is appended at the invoke phase and thus the exception is triggered after the invocation.
> At least in the servicemix-cxf-bc component (which has it's own invoker) this leads to strange behaviour. 
> I think it should be appended at the pre_invoke phase.
> Christian

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