Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of taariql@gmail.com designates
 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <513DA214.4050509@ast.dfs.de>
References: <513A03B2.5070403@ast.dfs.de>
	<CALhQg-Y=PDXLcPOeTC7fj7axPr9Q0ERmDKGs6PdXdbg0HGchnQ@mail.gmail.com>
	<513DA214.4050509@ast.dfs.de>
Date: Mon, 11 Mar 2013 15:45:06 +0200
Message-ID: 
 <CAAm9yXVj8dh_eFAj-RTTz8yVWn0XvEpVsPU-GC+xk35sT10H0g@mail.gmail.com>
Subject: Re: base class for context component?
From: Taariq Levack <taariql@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=f46d04016b3b7daada04d7a66115

--f46d04016b3b7daada04d7a66115
Content-Type: text/plain; charset=ISO-8859-1

Hi Sven

Perhaps you've misunderstood the following...
"Defining the context component"

In this context(excuse me), what's meant is a bean definition.
You should just use the DefaultCamelContext to define your own context,
with it's own name as this one is blackbox, and it's own routes.

Taariq


On Mon, Mar 11, 2013 at 11:21 AM, Sven Bauhan <sven@ast.dfs.de> wrote:

> On 03/09/13 20:40, Henryk Konsek wrote:
>
>> Hi Sven,
>>
>>  I'm trying to build my own context component as described in
>>> http://camel.apache.org/**context.html<http://camel.apache.org/context.html>
>>> .
>>>
>> Actually Context Component is ready to use out of the box. You don't
>> need to create your own. Or if you have to, please share with us the
>> reasoning behind this need.
>>
>> Best regards.
>>
>>  No, you misunderstood me. I do not want to replace the Context Component
> in Camel, but I need a class to define it. In the example the listing shows
> just the definition of the route without class or method. My questions
> concers the place for the definition of DefaultCamelContext. Is there an
> interface definition for a class containing a context component?
>
> Thanks, Sven
>
>

--f46d04016b3b7daada04d7a66115--