Hi
A good idea is to check the unit tests of Camel components for
examples, as sometimes there are some tests that are good examples.
https://github.com/apache/camel/tree/master/components/camel-olingo2/camel-olingo2-component/src/test
On Tue, Aug 23, 2016 at 3:01 PM, Ahsan Ali Aslam
Hi
The code seems too complicated.
The pollEnrich has a timeout option you can use to set to a value, and
if there is no file then the timeout is hit, and the message body is
empty. You can then check for that and throw an exception. The
pollEnrich allows also to use an AggregationStrategy where
We love contributions
http://camel.apache.org/contributing
On Wed, Aug 24, 2016 at 9:35 PM, Alex Soto wrote:
> Yes, this is what I ended up doing. I followed the example of Camel’s Pool
> Builders NettyWorkerPoolBuilder and NettyServerBossPoolBuilder.
>
You can get it from the UnitOfWork on the exchange.
There is an expression which you can use to get it
String id = ExpressionBuilder.routeIdExpression().evaluate(exchange,
String.class);
On Thu, Aug 25, 2016 at 4:08 AM, Rajith Muditha Attapattu
wrote:
> I'm overriding
No this is not configurable.
You are welcome to log a JIRA and if possible work on a patch / PR.
http://camel.apache.org/contributing
We could introduce an option you can configure on CamelContext ->
properties. That the message history can use to know the width limit.
On Wed, Aug 24, 2016 at
Hi,
I'm very new in apache camel.
I have integration route.
It uses pollEnrich to poll from file, and than aggregation strategy. I want,
that, if file is not available, than FileNotFoundException would be thrown
and handled by camel context.
Here is the piece of the route:
I'm overriding debugBefore and debugAfter in my test.
I'm using CamelTestSupport
The test involves multiple sub-routes called by the Route I'm testing.
I'm using the above methods to create a trail.
I'm wondering how I could grab the routeId of the route the exchanging
is passing through.
Great job on the CDI integration with OSGi support. It's really fantastic.
The only thing I've noticed is that the CDI runner for the unit tests will
pick up the Camel route tests but doesn't run the other tests that are
decorated with @RunWith(CamelCdiRunner.class)
Not a huge issue as the
Hi,
When an exception is thrown and the Message History is dumped, each of the
columns appears to be truncated beyond a certain length:
Message History
---
RouteId
Yes, this is what I ended up doing. I followed the example of Camel’s Pool
Builders NettyWorkerPoolBuilder and NettyServerBossPoolBuilder.
NettyWorkerPoolBuilder has a destroy method, although it does not actually wait
for completion, and NettyServerBossPoolBuilder does not even have a
Hmm. I'll have to give it a shot and see if it works for me in Fuse. Are
you using PropertyInject for that or just getter/setter?
Brad
On Wed, Aug 24, 2016 at 10:33 AM, Mark wrote:
> I agree. Its working, leave it alone. Maybe someday I'll port the Java
> DSL to XML.
You can maybe build your own pojo that shutdown the pool and has a
void method so you can use destroy-method in the blueprint xml file.
On Wed, Aug 24, 2016 at 4:25 PM, Alex Soto wrote:
> Hello,
>
> Is there a way to destroy the Netty (Boss or Worker) thread pools when
I agree. Its working, leave it alone. Maybe someday I'll port the Java
DSL to XML.
I did check and I'm using version 1.1 of the blueprint CM.
Thanks,
Mark
On Wed, Aug 24, 2016 at 10:11 AM, Brad Johnson wrote:
> If the update strategy is working you shouldn't
Hello,
Is there a way to destroy the Netty (Boss or Worker) thread pools when using
BluePrint xml?
I am trying this:
But Blueprint does not like the shutdownGracefully method because it is not a
void method (it returns Future).
What are other people doing in this case?
(I am using Camel
If the update strategy is working you shouldn't have to reload the bundle
and shouldn't have to specify ext:location. But if specifying the location
works then what the heck. But the blueprint-cm version should fix the
problems for you.
Brad
On Tue, Aug 23, 2016 at 10:25 PM, Brad Johnson
Right now we are about to production and we can't upgrade to camel
latest version.
Below is on camel 2.12.0 but it is working on camel 2.15.1.
Is there any work around to overcome on camel 2.12.0?
We have observed that "[]" are getting removed from soap response.
We have service, which
16 matches
Mail list logo