You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Henryk Konsek (JIRA)" <ji...@apache.org> on 2015/10/25 21:48:27 UTC

[jira] [Resolved] (CAMEL-9245) camel-paho - Endpoint should allow a flexible naming.

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

Henryk Konsek resolved CAMEL-9245.
----------------------------------
    Resolution: Fixed

> 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)