[
https://issues.apache.org/jira/browse/CAMEL-18783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651134#comment-17651134
]
Lukas Lowinger commented on CAMEL-18783:
----------------------------------------
[~ppalaga] It was automatically verified by upgrade to 3.20.0 in CQ repository
- eg. we have to apply those changes
https://github.com/apache/camel-quarkus/commit/b115a4b25013098af1024f201fa13e18eb441fb8
as we alter (which shouldn't be allowed) CXFEndpoint in ApplicationScope.
> camel-cxf - avoid referring Singleton bean instance(CxfEndpoint) while
> changing its state in different URIs
> -----------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-18783
> URL: https://issues.apache.org/jira/browse/CAMEL-18783
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 3.18.3
> Reporter: Lukas Lowinger
> Assignee: Freeman Yue Fang
> Priority: Minor
> Fix For: 3.20.0
>
>
> Having one `cxf:bean:soapClientEndpoint` (with Singleton scope) and following
> two routes
> {code}
> from("direct:simpleUriBean")
> .to("cxf:bean:soapClientEndpoint?dataFormat=PAYLOAD");
> from("direct:operandsAdd")
> .to("cxf:bean:soapClientEndpoint?dataFormat=POJO");
> {code}
> Leads to situation, that invoking route via `direct:simpleUriBean` will use
> `dataFormat=POJO` instead of PAYLOAD (which reader of that code could
> expect). Could we somehow detect those misuses of URI options ?
> Eg. printing WARNING: You are using URI option dataFormat which wasn't taken
> into account because you are using shared bean with Singleton scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
