Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <290341597.1249309055781.JavaMail.jira@brutus>
Date: Mon, 3 Aug 2009 07:17:35 -0700 (PDT)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-1873) template , consumerTemplate, service,
 proxy can't be set with right camel context if there are more than one
 camel context in the spring application context
In-Reply-To: <327603901.1249304015716.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-1873.
---------------------------------

    Resolution: Fixed

camel-trunk
http://svn.apache.org/viewvc?rev=800340&view=rev
http://svn.apache.org/viewvc?rev=800340&view=rev
camel-1.x branch
http://svn.apache.org/viewvc?rev=800394&view=rev

> template , consumerTemplate, service, proxy can't be set with right camel context if there are more than one camel context in the spring application context
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1873
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1873
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 1.6.2, 2.0.0
>
>
> Current camel support to define a producer template OUTSIDE a camel context, I think it works well just like the autowire function which is provided in Spring.
> If there more than two Camel context in the Spring Application context , the user should specify the camel context which the template should use.
> But I have a concern that even we put the template INSIDE the camel context, the template will not be set with a right version of camel context, since we use a CamelPostProcessor to inject CamelContext.
> So I did a quick test on the current Camel code and found there is a bug  if there are more one CamelContext -- CamelPostProcessor will inject the last create camel context into the CamelContextAware object. 
> Since it is not easy to add the camelContext referece id into the template element attribute, we'd better just support to parser these elements inside the camel context.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.