You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Lars Ködderitzsch (JIRA)" <ji...@apache.org> on 2017/10/25 11:15:03 UTC

[jira] [Comment Edited] (CXF-7534) Bus set on jaxws-endpoint is not honored anymore

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

Lars Ködderitzsch edited comment on CXF-7534 at 10/25/17 11:14 AM:
-------------------------------------------------------------------

I've created a small test project which shows the problem using a very stripped down version of our CXF setup.
I hope a gradle project is ok.
The included unit test fails with cxf < 3.1.10 and succeeds with 3.1.10. To use different versions just change the cxfVersion variable in build.gradle


was (Author: lkoe):
I've create a small test project which shows the problem using a very stripped down version of our CXF setup.
I hope a gradle project is ok.
The included unit test fails with cxf < 3.1.10 and succeeds with 3.1.10. To use different versions just change the cxfVersion variable in build.gradle

> Bus set on jaxws-endpoint is not honored anymore
> ------------------------------------------------
>
>                 Key: CXF-7534
>                 URL: https://issues.apache.org/jira/browse/CXF-7534
>             Project: CXF
>          Issue Type: Bug
>          Components: Bus, JAX-WS Runtime
>    Affects Versions: 3.1.11, 3.2.0
>            Reporter: Lars Ködderitzsch
>             Fix For: NeedMoreInfo
>
>         Attachments: cxf-7534-test.zip
>
>
> We're setting up a bus for our JAX-WS endpoints with custom features/interceptors  to handle some cross-cutting concerns.
> This worked quite well up until cxf-3.1.10. In all following versions, however, the interceptors are not triggered anymore.
> Some debugging revealed that while the endpoint is being initialized with the correct bus, at runtime a different bus instance (one that holds only a single PolicyInInterceptor) is being used.
> Please advise how the cause can be pinned down, I'm a bit lost in the internal complexities of CXF...
> Sample configuration:
> {code:xml}
>     <cxf:bus bus="geco.proton.jaxws.bus">
>         <cxf:features>
>             <ref bean="geco.proton.common.httpMetricsFeature" />
>             <ref bean="geco.proton.common.jaxws.soapMessageLoggingFeature" />
>             <ref bean="geco.proton.common.jaxws.konsensSoapHeaderFeature" />
>         </cxf:features>
>         <cxf:inInterceptors>
>             <ref bean="geco.proton.common.jaxws.endpointDeactivatingInterceptor" />
>             <ref bean="geco.proton.common.jaxws.globalAttachmentCachingInterceptor" />
>         </cxf:inInterceptors>
>         <cxf:outFaultInterceptors>
>             <ref bean="geco.proton.common.jaxws.globalKonsensAwareFaultInterceptor" />  
>         </cxf:outFaultInterceptors>
>     </cxf:bus>
>             <jaxws:endpoint id="contr.iorouter.v1.ControllerIORouterWS"
>                 bus="geco.proton.jaxws.bus"
>                 address="${services.intern.iorouter-ev-v1.settings[@endpointAddress]}" implementor="#contr.iorouter.v1.ControllerIORouterWSImpl"
>                 wsdlLocation="${services.intern.iorouter-ev-v1.settings[@wsdlLocation]}" endpointName="ns:ControllerEV"
>                 serviceName="ns:ControllerEV" xmlns:ns="http://finkonsens.de/geco/controller/ev/v1">
>                 <jaxws:properties>
>                     <entry key="schema-validation-enabled" value="${services.intern.iorouter-ev-v1.settings[@schemaValidationEnabled]}" />
>                     <entry key="mtom-enabled" value="${services.intern.iorouter-ev-v1.settings[@mtomEnabled]}" />
>                 </jaxws:properties>
>             </jaxws:endpoint>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)