[
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970821#comment-14970821
]
Henryk Konsek commented on CAMEL-9245:
--------------------------------------
Actually publishing to {{input/2}} is what I would expect to happen. You are
sending a message to the {{input/2}}, so this is published to {{input/2}} :) .
BTW a component naming is handled by the Camel Core and is outside of the scope
of the component.
Are you sure it behaves wrong?
> 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)
