[
https://issues.apache.org/jira/browse/CXF-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981131#comment-15981131
]
Christian Schneider commented on CXF-7344:
------------------------------------------
So seems ActiveMQ is not so strict .. still we must not send such properties
as it will be incompatible to many brokers.
I talked to Sergey. The idea is that we change the client to send correct
properties. On the server side we will change it so that it can work with the
old properties as well as with the new correct ones.
> REST on JMS Transport Fails with Invalid JMS Property
> -----------------------------------------------------
>
> Key: CXF-7344
> URL: https://issues.apache.org/jira/browse/CXF-7344
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, JMS, Transports
> Affects Versions: 3.1.10
> Reporter: Karthik Prasad
> Assignee: Christian Schneider
>
> I'm trying to create multiple channels for REST such that my endpoints can be
> invoked from Browser using http protcol or other applications can
> asynchronously invoke by placing message on queue. Though I'm able to
> configure both transport types. I'm able to access the REST service and but
> fails when sending JMS message
> Adding the below stackoverflow question I had asked. The link contains entire
> code I'm using with embedded JMS queue.
> http://stackoverflow.com/questions/43226697/rest-on-jms-transport-instead-of-http
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
