You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2012/10/02 20:41:08 UTC
[jira] [Created] (CAMEL-5676) Allow customer listener container in
camel-jms
Jonathan Anstey created CAMEL-5676:
--------------------------------------
Summary: Allow customer listener container in camel-jms
Key: CAMEL-5676
URL: https://issues.apache.org/jira/browse/CAMEL-5676
Project: Camel
Issue Type: Improvement
Affects Versions: 2.10.1
Reporter: Jonathan Anstey
Assignee: Jonathan Anstey
Fix For: 2.11.0, 2.10.2
In order to support Oracle Advance Queue's ADT JMS message type, we need to be able to override createConsumer on the Spring DMLC (see http://blog.javaforge.net/post/30858904340/oracle-advanced-queuing-spring-custom-types). We can do this by allowing for a custom message listener container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5676) Allow custom listener container in
camel-jms
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey updated CAMEL-5676:
-----------------------------------
Summary: Allow custom listener container in camel-jms (was: Allow customer listener container in camel-jms)
> Allow custom listener container in camel-jms
> --------------------------------------------
>
> Key: CAMEL-5676
> URL: https://issues.apache.org/jira/browse/CAMEL-5676
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.10.1
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.11.0, 2.10.2
>
>
> In order to support Oracle Advance Queue's ADT JMS message type, we need to be able to override createConsumer on the Spring DMLC (see http://blog.javaforge.net/post/30858904340/oracle-advanced-queuing-spring-custom-types). We can do this by allowing for a custom message listener container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5676) Allow custom listener container in
camel-jms
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468483#comment-13468483 ]
Jonathan Anstey commented on CAMEL-5676:
----------------------------------------
Ah yeah, great idea Claus. Will hopefully look at that later today.
Cheers,
Jon
> Allow custom listener container in camel-jms
> --------------------------------------------
>
> Key: CAMEL-5676
> URL: https://issues.apache.org/jira/browse/CAMEL-5676
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.10.1
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.11.0, 2.10.2
>
>
> In order to support Oracle Advance Queue's ADT JMS message type, we need to be able to override createConsumer on the Spring DMLC (see http://blog.javaforge.net/post/30858904340/oracle-advanced-queuing-spring-custom-types). We can do this by allowing for a custom message listener container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5676) Allow custom listener container in
camel-jms
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468323#comment-13468323 ]
Claus Ibsen commented on CAMEL-5676:
------------------------------------
I think we should introduce a factory interface for creating the custom message listener container. Then you can set this on the jms component, and have it work out of the box for all endpoints.
The factory would also help with creating a new listener container for each endpoint needed it. The current code doesn't support this well.
> Allow custom listener container in camel-jms
> --------------------------------------------
>
> Key: CAMEL-5676
> URL: https://issues.apache.org/jira/browse/CAMEL-5676
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.10.1
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.11.0, 2.10.2
>
>
> In order to support Oracle Advance Queue's ADT JMS message type, we need to be able to override createConsumer on the Spring DMLC (see http://blog.javaforge.net/post/30858904340/oracle-advanced-queuing-spring-custom-types). We can do this by allowing for a custom message listener container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5676) Allow custom listener container in
camel-jms
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey resolved CAMEL-5676.
------------------------------------
Resolution: Fixed
> Allow custom listener container in camel-jms
> --------------------------------------------
>
> Key: CAMEL-5676
> URL: https://issues.apache.org/jira/browse/CAMEL-5676
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.10.1
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.11.0, 2.10.2
>
>
> In order to support Oracle Advance Queue's ADT JMS message type, we need to be able to override createConsumer on the Spring DMLC (see http://blog.javaforge.net/post/30858904340/oracle-advanced-queuing-spring-custom-types). We can do this by allowing for a custom message listener container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira