[
https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894616#comment-15894616
]
Ryan Yeats commented on CAMEL-10918:
------------------------------------
To be honest that is what I thought was going to happen which wouldn't have
been a big deal for me since I am using artemis but never the less I tested it
with activemq and karaf and surprisingly it worked fine other than the no such
method exception when I tried to do something only supported by JMS 2.0. The
only troubling thing for me is its not clear to me exactly why that was
possible either I thought I would get some sort of class miss-match exception.
I'm tried it with both
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
and
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
> JMS 2.0 shared subscriptions
> ----------------------------
>
> Key: CAMEL-10918
> URL: https://issues.apache.org/jira/browse/CAMEL-10918
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
> Reporter: Ryan Yeats
> Priority: Minor
>
> This is presumptions of me and I apologize for that and will understand if
> this is closed outright but I was going to fork camel-sjms and add support
> for some JMS 2.0 for my own uses and during testing found out that it was
> still backwards compatible and figured I would contribute it back if you guys
> found it worth maintaining.
> Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a
> NoSuchMethodException as expected but everything else seemed to work. Also
> tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked.
> Here is the changeset:
> https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)