[jira] [Updated] (CAMEL-18783) camel-cxf - avoid referring Singleton bean instance(CxfEndpoint) while changing its state in different URIs

["Freeman Yue Fang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-18783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Yue Fang updated CAMEL-18783:
-------------------------------------
    Summary: camel-cxf - avoid referring Singleton bean instance(CxfEndpoint) while changing its state in different URIs  (was: camel-cxf - avoid referring singlton )

> 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
>            Priority: Minor
>
> 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)