Return-Path: 
 <dev-return-25023-apmail-camel-dev-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-dev-archive@www.apache.org
Received: (qmail 85866 invoked from network); 20 Jan 2011 08:40:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 20 Jan 2011 08:40:11 -0000
Received: (qmail 30994 invoked by uid 500); 20 Jan 2011 08:40:11 -0000
Delivered-To: apmail-camel-dev-archive@camel.apache.org
Received: (qmail 30079 invoked by uid 500); 20 Jan 2011 08:40:08 -0000
Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@camel.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@camel.apache.org>
List-Post: <mailto:dev@camel.apache.org>
List-Id: <dev.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list dev@camel.apache.org
Received: (qmail 30062 invoked by uid 500); 20 Jan 2011 08:40:07 -0000
Delivered-To: apmail-activemq-camel-dev@activemq.apache.org
Received: (qmail 30055 invoked by uid 99); 20 Jan 2011 08:40:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 08:40:06 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 08:40:06 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0K8djOW016265
	for <camel-dev@activemq.apache.org>; Thu, 20 Jan 2011 08:39:46 GMT
Message-ID: <21477731.77381295512785817.JavaMail.jira@thor>
Date: Thu, 20 Jan 2011 03:39:45 -0500 (EST)
From: "james strachan (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Created: (CAMEL-3563) CamelContext should act like a
 Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)
--------------------------------------------------------------------------------------------------------

                 Key: CAMEL-3563
                 URL: https://issues.apache.org/jira/browse/CAMEL-3563
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
            Reporter: james strachan
             Fix For: 2.6.0


Imagine you have a camelContext.xml for production use (e.g. you're creating an OSGi bundle with a camelContext.xml) but you want to create an integration test case that tests out your route.

So you want to create a new Camel XML file, testCamel.xml which includes the camelContext.xml and interacts with it. You now have 2 camelContexts. The test route needs to be able to refer to any endpoints inside the other camelContext.xml.

CamelContext has an ID (by default camelContext IIRC).

so if we have 

camelContext.xml
{code}
<camelContext id="prod" ...>
  <route> 
    <from uri="direct:foo">
     ...

{code}


testCamelContext.xml
{code}
<camelContext id="test" ...>
  <route> 
    <from uri="direct:start">
    <to uri="prod:direct:foo"/>
   </route>
  <route> 
    <from uri="prod:seda:bar">
    <to uri="mock:results"/>
   </route>
{code}

i.e. in the test case we are routing from our local CamelContext into the production camel context's "direct:start" endpoint and consuming from its "seda:bar" endpoint.

i.e. we use "prod" as a name, look it up in the IoC context (just like any other Component), but if its a CamelContext we (via TypeConverters) turn it into a Component that resolves the rest of the name


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