Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 20 Oct 2017 15:05:00 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13110668.1508418691000.18692.1508511900118@Atlassian.JIRA>
In-Reply-To: <JIRA.13110668.1508418691000@Atlassian.JIRA>
References: <JIRA.13110668.1508418691000@Atlassian.JIRA> <JIRA.13110668.1508418691018@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CXF-7534) Bus set on jaxws-endpoint is not
 honored anymore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 20 Oct 2017 15:05:05 -0000


    [ https://issues.apache.org/jira/browse/CXF-7534?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D162127=
61#comment-16212761 ]=20

Daniel Kulp commented on CXF-7534:
----------------------------------

You are likely going to need to create a test case for this.  I just did a =
"git diff cxf-3.1.10 cxf-3.1.11" and I don't see ANYTHING in the diff that =
would have any impact on the bus that is being used.   Also, two tests that=
 I know use unique busses defined like that (core/src/test/java/org/apache/=
cxf/bus/spring/BusDefinitionParserTest.java and core/src/test/java/org/apac=
he/cxf/bus/spring/SpringBusFactoryTest.java) both pass.=20


> 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=C3=B6dderitzsch
>             Fix For: NeedMoreInfo
>
>
> We're setting up a bus for our JAX-WS endpoints with custom features/inte=
rceptors  to handle some cross-cutting concerns.
> This worked quite well up until cxf-3.1.10. In all following versions, ho=
wever, 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 int=
ernal complexities of CXF...
> Sample configuration:
> {code:xml}
>     <cxf:bus bus=3D"geco.proton.jaxws.bus">
>         <cxf:features>
>             <ref bean=3D"geco.proton.common.httpMetricsFeature" />
>             <ref bean=3D"geco.proton.common.jaxws.soapMessageLoggingFeatu=
re" />
>             <ref bean=3D"geco.proton.common.jaxws.konsensSoapHeaderFeatur=
e" />
>         </cxf:features>
>         <cxf:inInterceptors>
>             <ref bean=3D"geco.proton.common.jaxws.endpointDeactivatingInt=
erceptor" />
>             <ref bean=3D"geco.proton.common.jaxws.globalAttachmentCaching=
Interceptor" />
>         </cxf:inInterceptors>
>         <cxf:outFaultInterceptors>
>             <ref bean=3D"geco.proton.common.jaxws.globalKonsensAwareFault=
Interceptor" /> =20
>         </cxf:outFaultInterceptors>
>     </cxf:bus>
>             <jaxws:endpoint id=3D"contr.iorouter.v1.ControllerIORouterWS"
>                 bus=3D"geco.proton.jaxws.bus"
>                 address=3D"${services.intern.iorouter-ev-v1.settings[@end=
pointAddress]}" implementor=3D"#contr.iorouter.v1.ControllerIORouterWSImpl"
>                 wsdlLocation=3D"${services.intern.iorouter-ev-v1.settings=
[@wsdlLocation]}" endpointName=3D"ns:ControllerEV"
>                 serviceName=3D"ns:ControllerEV" xmlns:ns=3D"http://finkon=
sens.de/geco/controller/ev/v1">
>                 <jaxws:properties>
>                     <entry key=3D"schema-validation-enabled" value=3D"${s=
ervices.intern.iorouter-ev-v1.settings[@schemaValidationEnabled]}" />
>                     <entry key=3D"mtom-enabled" value=3D"${services.inter=
n.iorouter-ev-v1.settings[@mtomEnabled]}" />
>                 </jaxws:properties>
>             </jaxws:endpoint>
> {code}


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