Yes, weaveById works fine, but in my case I use it in a base class, used by
almost every integration test and those tests are able to modify the route
too before start, so I can't be sure that my originally first node is really
still the first after the child test set up phase, that's why I used an
Thanks Ranx, the documentation actually says, that "It is recommended to only
advice a given route once".
I use advice on 2 separate route, those just built by 1 route builder, so
based on the documentation, shouldn't have any kind of error.
--
View this message in context:
http://camel.465427.
@Sashika
I was just looking at that again right before I read your email. I created
and added a quick unit test to the thread. Basically the producer template
does inOnly when you do a sendBody and InOut when requestBody is used. If
it weren't already getting late I'd probably log the Exchange
By the way I did a quick test out of curiosity and you might find the
results interesting. It uses the exact same routes and producer template
to fire messages. One is sent in fire and forget "sendBody" and the other
is sent request reply with "requestBody".
The fire and forget at the end of the
Thanks Matt, so inOnly("direct:XXX") will not be asynchronous.
However what about the other side of the question (which is what I am mostly
intrested in)? Why isn't the OUT message lost at the end of the
[.inOnly("direct:BBB")] call?
I think I can summarise my question as follows :
How is [.inO
I've noticed the fire and forget only works with seda end point called with
inOnly.
On Sep 26, 2016 02:31, "Brad Johnson" wrote:
> @Sim
>
> By the way, even if you set that to seda queue it's possible you'd get
> different responses depending on thread execution order. As far as I know
> Camel
Hello,
Why can't you use 'workerCount' option? It overrides the default number of
threads for Netty.
http://camel.apache.org/netty.html
Best regards,
Tadayoshi
On Sat, Sep 24, 2016 at 3:58 PM, jayashankar wrote:
> Using camel netty component redhat version 2.12.X version to consume TCP
> requ
Hello,
Whether or not it's a standard practice, I don't think there is any other
good approach than either mocking the component and checking the headers,
or using an embedded Jetty server inside the test case. Also, such kind of
integration test should be more reliable if you want to repeatedly c
@Sim
By the way, even if you set that to seda queue it's possible you'd get
different responses depending on thread execution order. As far as I know
Camel is doing a shallow clone there so if you changed the body in the seda
route it might still show up, on occasion, as showing exactly the same
The direct is going to return a message regardless of what the upstream
components say because at that point you are indicating that you *do *want
that route to return something to you. Much like a method with a void
return calling a second method that returns a String. Just because the
calling m
We generally have built single route and use the thread pool mechanism to
handle load. I think default is 1000 max pool. Now if the transformation
requirement is not too much variable, it works wonderfully.
Or start and stop is associated with spring application context. And yes if you
want to
Look at using. The transport can be anything of course but direct-vm
usually works pretty well.
direct-vm:${header.operationName}
On Fri, Sep 23, 2016 at 4:30 PM, Kasim Sert (Ibtech-Software
Infrastructure) wrote:
> Hi,
>
> I have more than 2 thousands web services(SOAP/REST) and want to move
The direct component is synchronous (it's implemented by simply executing
the next Processor in the route). If you want to do it asynchronously, you
can use the seda component which uses a BlockingQueue and a thread pool or
one of the non-core components like disruptor, activemq, amqp, etc.
The In
Hi colleagues
Is it possible to set the known host of a sftp server call using byte array?
Saw the configuration and found it to have only file connection.
We can't use file system in our use case.
Regards
Arpit.
Sent from my iPhone
The Camel community announces the immediate availability of the new
patch release Camel 2.16.4, the last planned release for the 2.16.x
branch. This release contains over 50 bug fixes and improvements
applied in the past months on the Camel 2.16.x branch.
The artifacts are published and ready for
If InOnly works asynchronous then why does it wait for "direct:BBB" to finish
before the next step is executed?
For example take the following code:
[code]
from("jetty:http://localhost:8282/";)
.log("Hello From A")
.inOnly("direct:BBB") // asynchr
Hi,
I locate the problem in the code.
but I have not found yet, solution.
in
https://github.com/apache/camel/blob/master/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/converters/MongoDbBasicConverters.java
there are some (DBObject) JSON.parse(s);
But JSON is a simple p
Below are my web-service request , Route and Request-Validator,
Web-service request:
http://schemas.xmlsoap.org/soap/envelope/";>
http://services.sabre.com/STL_Header/v02_01";>
GetHotelMediaRQ
CID12345
AppTest
05EFPElI2A4KudU75863JIxqAhQJtAx0
4DT
18 matches
Mail list logo