Hi
I'm implementing a request reply over JMS using the
replyToDestinationSelectorName to correlate the respons. Now I would like to
controll the actual value set on the correlation property. i.e something
like replyToDestinationSelectorValue. Is there a way to do this?
Looking at the code it
OK, I'm a bit more knowledgeable now...
The first issue is that I thought I created a pool of 1 thread.
ShlomiJ wrote
ThreadPoolBuilder tpBuilder = new ThreadPoolBuilder(this.context);
ExecutorService wiretapThreadpool =
Thanks for clearing that out anyway i will be using blueprint for my service
dependency management . It has all the spring goodies so porting my project
will be easy . Main reason for choosing blueprint was avoiding different
xml's for components and camel routes ,beans ..etc . while in blueprint
On Tue, Mar 13, 2012 at 9:27 AM, Peter Bromander
peter.broman...@gmail.com wrote:
Hi
I'm implementing a request reply over JMS using the
replyToDestinationSelectorName to correlate the respons. Now I would like to
controll the actual value set on the correlation property. i.e something
like
Problem with this solution is that SyslogAppender limits packet to 1024bytes.
Additionally I do not like the idea, that part of the camel configuration is
kept in *log4j.configuration (appender, format), but this argument is very
personal :D
--
View this message in context:
On Tue, Mar 13, 2012 at 9:13 AM, ShlomiJ shlomij...@gmail.com wrote:
OK, I'm a bit more knowledgeable now...
The first issue is that I thought I created a pool of 1 thread.
ShlomiJ wrote
ThreadPoolBuilder tpBuilder = new ThreadPoolBuilder(this.context);
ExecutorService wiretapThreadpool =
Hi
See ticket
https://issues.apache.org/jira/browse/CAMEL-5079
On Tue, Mar 13, 2012 at 11:00 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Tue, Mar 13, 2012 at 9:13 AM, ShlomiJ shlomij...@gmail.com wrote:
OK, I'm a bit more knowledgeable now...
The first issue is that I thought I created a
Btw. which OSGi server do you use. If you do not use it already I can
really recommend using Apache Karaf. Installing camel on it is just as
easy as executing two commands.
I have a tutorial for camel with Apache Karaf if you want to try it:
http://www.liquid-reality.de/x/G4Bk
Christian
Am
i have been using apache servicemix for its ESB for a long time . But , never
used its osgi features till now
-
thanks
sanketh
mail : san...@gmail.com
--
View this message in context:
Hello,
suppose this route :
from(file://{{extra.inputDir}})
.routeId(start)
.*bean*(EnterpriseServiceUtils.class,define)..
simple question to be sure :
Is this kind of bean definition creates a singleton or Camel creates a new
On Tue, Mar 13, 2012 at 1:07 PM, jmh jeanmarc.her...@nrb.be wrote:
Hello,
suppose this route :
from(file://{{extra.inputDir}})
.routeId(start)
.*bean*(EnterpriseServiceUtils.class,define)..
simple question to be sure :
Is this
Hi
When upgrading from Apache Camel 2.9.0 to 2.9.1 I suddently get an error
when using camel-cxf endpoints.
I have defined this endpoint:
and use it in this route:
When running my JUnit tests (extending CamelSpringTestSupport) I get this
exception:
When I debug my test I see that the
Hi
Do you use any interceptor in your unit test such as indicate in the stacktrace?
InterceptSendToEndpoint
Can you post the code snippet where you use that?
On Tue, Mar 13, 2012 at 2:25 PM, hefiso
henrik.filtenborg.soren...@gmail.com wrote:
Hi
When upgrading from Apache Camel 2.9.0 to
Hi thanks for the quick reply.
So what you're saying is that currently the only way to correlate a JMS
reply is using msgId, corrId or the UUID?
We have a case where we would like to correlate using a JMS property e.g
myCorrId and as a said before we would like to control the value of this
Claus Ibsen-2 wrote
When you provide an existing thread pool to any Camel EIPs, such as
the WireTap, then
YOU are in control of the lifecycle of the thread pool. So you have to
shutdown this thread pool yourself,
when its no longer in-use.
I understand your point about the life cycle. But I
On Tue, Mar 13, 2012 at 3:18 PM, ShlomiJ shlomij...@gmail.com wrote:
Claus Ibsen-2 wrote
When you provide an existing thread pool to any Camel EIPs, such as
the WireTap, then
YOU are in control of the lifecycle of the thread pool. So you have to
shutdown this thread pool yourself,
when its
I only use a mocked endpoint in my test:
The problem still exists if I remove the mocked endpoint and
InterceptSendToEndpoint is still in the StackTrace... I do not know the
origin of InterceptSendToEndpoint in the stacktrace, but perhaps it comes
from using ? However, I really don't know :-/
On Tue, Mar 13, 2012 at 3:04 PM, Peter Bromander
peter.broman...@gmail.com wrote:
Hi thanks for the quick reply.
So what you're saying is that currently the only way to correlate a JMS
reply is using msgId, corrId or the UUID?
We have a case where we would like to correlate using a JMS
Thanks for the information.
I wrote a custom iterator which makes calls to my underlying service on a
page-by-page base (passing each time the start position and fetch size).
The JPA interface supports this kind of queries.
The splitter does the rest.
The more I play with Camel with the more I'm
Can someone please give some guidance. As per 2.4 servlet spec, Listners
(ContexLoaderListener) are loaded first before the servlets in the
container. I am unsure how can this work. When the spring context is
loaded it will never find the necessary component to resolve the route with
Thanks for the very good feedback. We are pleased you like Apache Camel.
Keep riding the Camel... ;o)
Best,
Christian
On Tue, Mar 13, 2012 at 3:57 PM, Walter De Wit walte...@gmail.com wrote:
Thanks for the information.
I wrote a custom iterator which makes calls to my underlying service on a
Within the file2 component, noop=true specifies that idempotent=true will
be set automatically. However, based upon a user initiated action I need
to poll a directory endpoint and obtain a list of files present. The
auto-set of idempotent=true creates problems as I'm not always able to read
David,
could you please have a loot at this whether you see a way to support both
versions (Spring 3.0 and 3.0). At present we only discovered an issue with
the CamelSpringTestContextLoader which is a new class added in Camel
2.10.0. If it's not possible, I'm +1 to postpone the changes we did for
I have a need to run multiple CometD endpoints where I can selectively
dispatch messages to each one based on data in my flow (splitting via
different comet subscriptions isn't sufficient). My plan was to run each
endpoint on it's own port so they wouldn't overlap but as soon as I try and
create a
We may add a profile in the camel-test-spring module and consider this
feature is only support in Spring 3.1.
We can let the profile pick up the dependency of spring-test and the
CamelSpringTestContextLoader at that time.
If the people want to have a try with the spring test , he need to
There are some enhancement on the camel-servlet since camel 2.7.x.
If you want to leverage the spring ContextLoaderListener to load the
file, you need to upgrade the camel that you use.
If not, you need to ask for commerical support as Apache Camel 2.4.0
is released for almost 2 years.
On
Hi,
Which version of Camel are you using ?
Do you deploy the Cometd producer and consumer at the same time ?
I guess you doesn't past all the routes those you have.
On Wed Mar 14 07:29:28 2012, Chris Geer wrote:
I have a need to run multiple CometD endpoints where I can selectively
dispatch
Just one comment on the camel-cxf behavior change of Camel 2.9.1.
CxfProducer create a new client when it is started to avoid the memory leak
if the customer create the route dynamically.
I'm not sure if it is relates to test code that you have, can you show us
the whole test example.
Willem
We are using Camel 2.8.3 with ServiceMix 4.4.1. The consumer is a webpage
using the jquery comet library. You are correct that I didn't publish all
my routes in the sample I provided, I just provided enough to show the
error.
I did some more experimenting and was able to start multiple cometd
Hi,
There is no requirement that the Producer be a Camel Netty producer to
communicate with a Camel Netty consumer. A straight Netty producer should
work with Camel Netty Consumer just fine.
It is more important to ensure that the communication handshake (one-way or
request/reply) are properly
30 matches
Mail list logo