You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/08/05 09:38:35 UTC
[jira] Commented: (CAMEL-1878) Bean component - invokes onMessage
from javax.jms.MessageListener even though a specific method name have been
provided
[ https://issues.apache.org/activemq/browse/CAMEL-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53465#action_53465 ]
Claus Ibsen commented on CAMEL-1878:
------------------------------------
See nabble
http://www.nabble.com/bean-binding-with-inheritance---2.0-M3-camel-http-td24802648.html
> Bean component - invokes onMessage from javax.jms.MessageListener even though a specific method name have been provided
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1878
> URL: https://issues.apache.org/activemq/browse/CAMEL-1878
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.6.1, 2.0-M3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.0.0
>
>
> This is only an issue when your bean implements javax.jms.MessageListener and then specify a specific method to use, then Camel will still prefer to use the onMessage method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.