You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/01/08 15:09:00 UTC
[jira] [Assigned] (CAMEL-16003) camel-rabbitmq - Rework component
using spring-rabbitmq
[ https://issues.apache.org/jira/browse/CAMEL-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-16003:
-----------------------------------
Assignee: Claus Ibsen
> camel-rabbitmq - Rework component using spring-rabbitmq
> -------------------------------------------------------
>
> Key: CAMEL-16003
> URL: https://issues.apache.org/jira/browse/CAMEL-16003
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.x
>
>
> Instead of our own home grown code, that over time has become harder to maintain due to many different "good attempts" but they have messed up the code.
> If we use spring-rabbitmq then we can reimplement the component and base it on how we do it for camel-jms that uses spring-jms.
> Then users can also use the spring cached connection factory etc. Also since rabbitmq is spring product then it makes sense to use their spring java client also.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)