[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178090#comment-14178090 ] Willem Jiang commented on CAMEL-4494: - Hi Jens, Current Apache JIRA just takes the submit action as granted with Apache license, so you don't need to do anything else this time. Regards, Willem > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176901#comment-14176901 ] Jens Granseuer commented on CAMEL-4494: --- I'd love to do so but I don't see where I can set that infamous X even when making a new attachment. Any pointers? > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176895#comment-14176895 ] Susan Javurek commented on CAMEL-4494: -- Hi Jens, We'd like to pick up your fix. Would you reattach the files so we can legally incorporate it into the product? Thank you, Susan > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1327#comment-1327 ] Claus Ibsen commented on CAMEL-4494: Yes you need to re-attach the file again. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff, > camel-jms-replyto2.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233260#comment-13233260 ] Claus Ibsen commented on CAMEL-4494: When attaching patches make sure to mark [x] in grant license to ASL, otherwise it cannot be used/accepted. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219329#comment-13219329 ] David J. M. Karlsen commented on CAMEL-4494: I definetly think it should use a DestinationResolver as the rest is spring based - and this is the strategy interface for destination resolving. This will allow for custom resolving: I have an custom implementation of a DestinationResolver in order to be able to set WMQ (WebSphere MQ) specific stuff on resolved queues. Where can I donate that code? It currently relies on some small parts of IBM code, but I could change that to being reflection based. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > Attachments: camel-jms-replyto.diff > > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203448#comment-13203448 ] Jens Granseuer commented on CAMEL-4494: --- Or consider the case where I am just trying to proxy a (obviously synchronous) HTTP request/reply pair via JMS. I'm not sure if that can even be done with two separate routes. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203398#comment-13203398 ] Jens Granseuer commented on CAMEL-4494: --- Hi Keith, yes, I guess this could be done using separate routes instead. Doing it in one synchronous route, however, does provide a few advantages, e.g. being able to access context information from the request not to mention that it simply results in a simpler route setup. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202802#comment-13202802 ] Heath Kesler commented on CAMEL-4494: - Hi Jens, are you trying to set this up as a single synchronous route? You can set it up asynchronously using multiple routes fairly easily. Just trying to clarify your use case. > Allow replyTo message header to be different from actual reply queue > > > Key: CAMEL-4494 > URL: https://issues.apache.org/jira/browse/CAMEL-4494 > Project: Camel > Issue Type: New Feature > Components: camel-jms >Affects Versions: 2.8.1 >Reporter: Jens Granseuer > > We have an application that acts as a JMS client in the following setup: > * a local queue manager (L) with queues for request (L.REQUEST) and reply > (L.REPLY) messages > * a remote queue manager (R) with queues for request (R.REQUEST) and reply > (R.REPLY) messages > The remote queue manager is unknown to the client application, and messages > sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there > is a server application listening on R.REQUEST, posting responses in R.REPLY. > The local queue manager is unknown to the server application. Messages sent > to R.REPLY are automatically forwarded to L.REPLY. > The client needs to put message in L.REQUEST and receive the reply in > L.REPLY. However, in the message header it must set R.REPLY as the reply > queue because L.REPLY is not known to the server application. > The Camel JMS component currently doesn't seem to support this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
