camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Koscejev (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-5655) Camel Endpoint ignores camelContextId property in Spring configuration
Date Thu, 27 Sep 2012 11:14:08 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464622#comment-13464622
] 

Anton Koscejev edited comment on CAMEL-5655 at 9/27/12 10:12 PM:
-----------------------------------------------------------------

Attached a test suite. It fails to create ApplicationContext (not on assert). Proxy requests
an endpoint by reference, which is found in Spring ApplicationContext, but with a different
CamelContext specified.
                
      was (Author: koscejev):
    Attached a test suite. It fail to create ApplicationContext (not on assert). Proxy requests
an endpoint by reference, which is found in Spring ApplicationContext, but with a different
CamelContext specified.
                  
> Camel Endpoint ignores camelContextId property in Spring configuration
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-5655
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5655
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint, camel-spring
>    Affects Versions: 2.10.1
>            Reporter: Anton Koscejev
>            Assignee: Claus Ibsen
>              Labels: camelContextId, endpoint, spring
>             Fix For: 2.9.4, 2.11.0, 2.10.2
>
>         Attachments: CAMEL-5655.zip
>
>
> Camel Endpoint, if configured outside camelContext element in Spring configuration, ignores
camelContextId property. 
> Steps to reproduce: Configure two contexts in spring configuration. Then in the same
config file configure two  endpoints outside camelContext, but with camelContextId specified.
Both endpoints will be created pointing to the same (first) camel context, despite being configured
to different contexts. Attempting to use them by reference results in failure, as endpoint
camelContext doesn't match the expected one.

--
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

Mime
View raw message