[
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970946#comment-14970946
]
Jaume Teixi commented on CAMEL-9245:
------------------------------------
When the *PahoComponent* is named *paho2* it is wrong because it is posting to
the topic {noformat}/input/2{noformat} (note the first slash) instead of
{noformat}input/2{noformat}
And if you name the *PahoComponent* to *mypaho* it will post to the wrong topic
{noformat}t://input/2{noformat}
This does not happens with other components like *camel-jms* or *camel-mqtt*
only with *camel-paho* so it seems not related to the Camel Core and maybe to
the Endpoint format definition or to the handling of it.
> camel-paho - Endpoint should allow a flexible naming.
> -----------------------------------------------------
>
> Key: CAMEL-9245
> URL: https://issues.apache.org/jira/browse/CAMEL-9245
> Project: Camel
> Issue Type: Improvement
> Components: camel-paho
> Reporter: Jaume Teixi
> Priority: Minor
>
> 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)
