[
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973434#comment-14973434
]
Henryk Konsek commented on CAMEL-9245:
--------------------------------------
Oh shit! Did I really commit that? What was on my mind to assume fixed
component name? :|
Anyway - I have fixed that in 2.17.0 (1) and 2.16.1 (2).
Thanks for reporting (and sorry for a stupid mistake)!
(1) 14e9236aca9e1cd93f180158767d7e102257f1b6
(2) e791fc27756fddce2eaa759c86250c8c5e7f9a0f
> camel-paho - Endpoint should allow a flexible naming.
> -----------------------------------------------------
>
> Key: CAMEL-9245
> URL: https://issues.apache.org/jira/browse/CAMEL-9245
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
> Affects Versions: 2.16.0
> Reporter: Jaume Teixi
> Priority: Minor
> Fix For: 2.17.0, 2.16.1
>
>
> If endpoint doesn't match exactly paho: it fails to publish to the correct
> topic.
> Once should be able in Spring to @Autowired two different PahoComponent
> pointing to different Application Context defined PahoComponent bean id'S.
> Currently if bean id is not named exactly paho it fails to publish to the
> correct topic and for example instead of input/1 publishes to t://input/1
> when id is mypaho instead of paho
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
