[
https://issues.apache.org/jira/browse/CAMEL-14216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981694#comment-16981694
]
Claus Ibsen commented on CAMEL-14216:
-------------------------------------
There is no alternative component, and yes it may not be active, but the STOMP
spec is also not active, its a dead spec.
I dont see a reason to remove it so aggresively. People in the community can
step up to help maintain the stomp client project etc.
At best you can do is to add a note in the docs.
> Remove Camel-stomp component
> -----------------------------
>
> Key: CAMEL-14216
> URL: https://issues.apache.org/jira/browse/CAMEL-14216
> Project: Camel
> Issue Type: Task
> Components: camel-stomp
> Affects Versions: 3.0.0
> Reporter: Omar Al-Safi
> Assignee: Omar Al-Safi
> Priority: Minor
> Fix For: 3.x
>
>
> Since Camel-stomp component is relying on
> [https://github.com/fusesource/stompjms/tree/master/stompjms-client] which
> looks like is no longer actively maintained, it will make sense to remove it
> from camel next releases in order to reduce the overhead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
