Hi,
I noticed a recent jira comment that indicates the context component is
deprecated[1] I couldn't find anything in the code or documentation that
indicates deprecation. Is there now a better alternative for the kinds of
use cases the context component supported?
[1]
wait for a response
before sending another segment.
To use this implementation as a library it is implemented in a camel
context component.
The sender has to wait for responses and if no response is received it
has to react after a given timeout time.
So I tried to implement this behaviour
address space but for the lifecycle of the endpoint as well.
>>
>> You can create a JIRA ticket and I'll review / test your patch.
>>
>> Antonin
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Context-Component-issue-tp5770975p5772383.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
tti wrote:
> Hi Aaron,
>
> I've been able to reproduce your issue and your analysis is correct.
>
> The Endpoint returned by the context component has its reference to its
> original black-box Camel context overwritten when the 'parent' context adds
> it to its list
Hi Antonin,
Thank you very much. Part of the patch involves having the Context
component mint 'exported' Endpoints that have noops for several operations
that looked dangerous to me (like setCamelContext).
I'll create an issue this evening, and place the fixes in a cloned
repos
Hi Aaron,
I've been able to reproduce your issue and your analysis is correct.
The Endpoint returned by the context component has its reference to its
original black-box Camel context overwritten when the 'parent' context adds
it to its list of service. There is a clear design
Hi All,
I had some time to dig into this issue, and it appears more severe than I
had initially thought. Right now, there is *no* isolation between endpoint
names between camel contexts. In fact, using the context component in its
current state results brings *local* endpoint names from
Hello,
I'm having a strange problem with the camel context component and think it
may be a bug. I've created a unit test that currently fails:
https://gist.github.com/birkland/1b12261521dd5d5c79ef
Basically, I'm trying create a 'parent' camel context that routes a m
Thanks for the speedy response Claus.
I gravitated towards using the combination of SEDA and context component
because I liked the pseudo-namespace provided by referencing the endpoint using
the context in which it was defined, i.e.
instead of
But if it isn't possible, I'
Hi
That is what the vm component is for
http://camel.apache.org/vm
Or the direct-vm
http://camel.apache.org/direct-vm
On Fri, Feb 21, 2014 at 3:24 PM, Cohen, Bruce wrote:
> I'm trying to use the context component with SEDA endpoints. My goal is to
> be able to define a SEDA endp
I'm trying to use the context component with SEDA endpoints. My goal is to be
able to define a SEDA endpoint in one context and have multiple consumers in
other contexts consuming from it, is this possible?
I have the following two Spring DSL XML configurations:
inne
ed to create a camel context component to put a route in a
> black box. But I want to put this context component into a library and hide
> it behind an API.
>
> Starting point was the description in http://camel.apache.org/context.html
> and the detailed example in
> http://svn.
Hi,
I think for the interface Registry a method bind() should be defined.
Here comes the explanation why:
Finally I managed to create a camel context component to put a route in
a black box. But I want to put this context component into a library and
hide it behind an API.
Starting point
are
>> asking about.
>>
> I did not mean to create a new implementation of DefaultCamelContext. I
> want to create a class for a context component.
>
>
>
>> And the docs you referred to discuss this, and it's the example for how to
>>
context component.
And the docs you referred to discuss this, and it's the example for how to
do so. You can copy that sample and redefine it like this for example...
DefaultCamelContext fooBlackBox = new DefaultCamelContext(registry);
fooBlackBox.setName("fooBlackBox");
fooBlackBo
issing for me, is how I can put it in a running context.
> Is there a small example that I could investigate to understand how it
> works?
>
> Thanks, Sven
>
>
> On 03/11/13 14:45, Taariq Levack wrote:
>
>> Hi Sven
>>
>> Perhaps you've misunderstoo
there a small example that I could investigate to understand how it
works?
Thanks, Sven
On 03/11/13 14:45, Taariq Levack wrote:
Hi Sven
Perhaps you've misunderstood the following...
"Defining the context component"
In this context(excuse me), what's meant is a bean definit
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
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.
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 w
Hi Sven,
> I'm trying to build my own context component as described in
> 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 nee
Hi,
I'm trying to build my own context component as described in
http://camel.apache.org/context.html.
I wonder if there is a base class or interface I can use for
MyContextComponent. I saw there exists org.apache.camel.Component. But
the method createEndpoint() I have to implement doe
/confluence/display/CAMEL/Context?focusedCommentId=30739765&#comment-30739765>
>
>
> Best regards,
> Robert
>
>
> Willem.Jiang wrote
> > Hi Robert,
> >
> > It is not a bug of camel.
> >
> > You need to make sure the context componen
Context?focusedCommentId=30739765&#comment-30739765>
Best regards,
Robert
Willem.Jiang wrote
> Hi Robert,
>
> It is not a bug of camel.
>
> You need to make sure the context component can load the sub context
> first.
> So we need add the depends-on attribute like thi
Hi Robert,
It is not a bug of camel.
You need to make sure the context component can load the sub context first.
So we need add the depends-on attribute like this
http://localhost:9090/foo"/>
http://foo.in)"/>
http://foo.in)"/>
--
Willem Jiang
Red Hat, Inc
g to build the (test) project. And I ran the
> application with the 'mvn camel:run' command using this (predefined) entry
> in the pom.xml:
>
>
> org.apache.camel
> camel-maven-plugin
> 2.10.1
>
>
> Do you think using the camel-java archetype would make any d
he pom.xml:
org.apache.camel
camel-maven-plugin
2.10.1
Do you think using the camel-java archetype would make any difference if the
context component is found? It looks like Maven finds the dependency and
it's just not picked up during route construction.
If
mel can't find the context component [1] in my application. My application
> is based on the Camel java maven archetype. I am declaring the camel-context
> maven dependency. What am I doing wrong?
>
> Here is my route declaration
>
>
>
> http://localhost:9090/foo&quo
Hi,
camel can't find the context component [1] in my application. My application
is based on the Camel java maven archetype. I am declaring the camel-context
maven dependency. What am I doing wrong?
Here is my route declaration
http://localhost:909
ent thread), the route in your context component will not be
part of this transaction.
from("vm:in").transacted().to(...).to("vm:out"); make no sense, because the
"vm" component doesn't support transactions, unless your to(...) talks to a
transacted resource.
Bes
We are planning to write a bunch of camel contexts which contain
routes using only local endpoints (the vm component). To get everyone
talking to one another, we'll create a "wiring" context which connects
the dots. I was wondering how this will work with transactions.
Suppose I have a few routes
our case). I'm trying to use the context component
(http://camel.apache.org/context.html), but I'm having some troubles.
When I try to refer to the local endpoints in other bundles, Camel
complains saying it can't find a component which supports the scheme
"context". Yes, I
Hi,
The options are related to the "direct" or "seda" endpoint options that you
are invoking using the context component. The options are not for
specialization of the context component itself.
Hope this hel
The text of http://camel.apache.org/context.html says:
"You can append query options to the URI in the following format,
?option=value&option=value&..."
However, it doesn't explain how to get to those parameter's from your
context. Looking through the code, I don't even see it passing those
param
33 matches
Mail list logo
