[
https://issues.apache.org/jira/browse/CAMEL-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130720#comment-13130720
]
Claus Ibsen commented on CAMEL-4503:
------------------------------------
CAMEL-4139 causes this problem, it will lookup existing bean by its id, and
reuse that as CxfEndpoint.
Even if CxfComponent is creating a new CxfEndpoint.
It seems the problem is that if you omit the address in the <cxf:cxfEndpoint>
in the XML file.
And then you want to use that <cxf:cxfEndpoint> bean but specific the address
at runtime. Then CxfComponent
will still hand out a shared CxfEndpoint.
It guess the tricky part is that with cxf:bean:xxx you refer to a bean, and
then you *also* provide additional configurations which should override.
This seems a hard path to support. Maybe cxf:bean:xxx should be made to not
accept any parameters at all, if that makes sense.
Alternative the cxf:bean:xxx should be sort of a template, and then being able
to create "clones" of itself.
> Recipient List cannot vary destination by changing property in an expression
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4503
> URL: https://issues.apache.org/jira/browse/CAMEL-4503
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.8.1
> Reporter: Jonathan Anstey
>
> This is probably due to producers being cached based on unresolved endpoint
> URI, rather than the resolved endpoint URI. Haven't tested this theory out
> though.
> See message on user list http://markmail.org/message/sdysp6sspq5lomf4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
