[ https://issues.apache.org/jira/browse/CAMEL-14221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahesh updated CAMEL-14221: --------------------------- Description: The STOMP version is hardcoded in the {{org.fusesource.stomp.client.Stomp}} class. Though the {{org.fusesource.stomp.client.Stomp}} class has setter method for version, the Camel-Stomp Component has not exposed that option to be set by the users. Looks like {{StompEndpoint}} and {{StompConfiguration}} classes would need changes to allow users to set version. STOMP 1.2 has been available for years and most of the message brokers support STOMP 1.2. In such scenarios it becomes a necessary feature for the camel-stomp to include the support for STOMP 1.2 was: The STOMP version is hardcoded in the {{org.fusesource.stomp.client.Stomp}} class. Though the {{org.fusesource.stomp.client.Stomp}} class has setter methods for version and custom headers, the Camel-Stomp Component has not exposed those options to be set by the users. Looks like {{StompEndpoint}} and {{StompConfiguration}} classes would need changes to allow users to set version and custom headers. STOMP 1.2 has been available for years and most of the message brokers support STOMP 1.2. In such scenarios it becomes a necessary feature for the camel-stomp to include the support for STOMP 1.2 > Stomp Component has no option to set version > -------------------------------------------- > > Key: CAMEL-14221 > URL: https://issues.apache.org/jira/browse/CAMEL-14221 > Project: Camel > Issue Type: New Feature > Components: camel-stomp > Affects Versions: 3.0.0.RC3 > Reporter: Mahesh > Priority: Major > Fix For: Future > > > The STOMP version is hardcoded in the {{org.fusesource.stomp.client.Stomp}} > class. Though the {{org.fusesource.stomp.client.Stomp}} class has setter > method for version, the Camel-Stomp Component has not exposed that option to > be set by the users. > Looks like {{StompEndpoint}} and {{StompConfiguration}} classes would need > changes to allow users to set version. > > STOMP 1.2 has been available for years and most of the message brokers > support STOMP 1.2. In such scenarios it becomes a necessary feature for the > camel-stomp to include the support for STOMP 1.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)