Thanks Ranx,
I was able to address logging by modifying the config file (it was set to
WARN). Now, my next step is to actually read the JSON. Since I can't read
it directly into POJO, I'm left using the generic unmarshal and reading the
data as a map. Is that something you can help with? My ja
By the way, I think I used to use:
< bean ref="StoreLoadBean" method="loadRetailStoreDataFromMap"/>
On Tue, Sep 27, 2016 at 6:26 PM, Brad Johnson
wrote:
> I'm going to assume that the method named there is on the bean. The log
> messages may be getting ignored due to the logger not being set
I'm going to assume that the method named there is on the bean. The log
messages may be getting ignored due to the logger not being set up
correctly. You can temporarily replace with System.out until you have time
to go back and make sure the logger is setup up correctly. As for the
loading of t
Hi Ranx,
You are correct that I need to get call a web service, get the response,
transform it, and send it to another system. The integration gets
information about stores and forwards it to a marketing system. We are
making the change because the database is going away.
Old: AutoStart -> Quer
Try jdbc:.*
Note the full stop.
If you look at the javadoc for isMockEndpointsAndSkip function, it refers you
to EndpointHelper.matchEndpoint which has the following
The match rules are applied in this order:
• exact match, returns true
• wildcard match (pattern ends with a * a
Hi Ibsen,
I see a case here that you responded earlier.
http://stackoverflow.com/questions/31312281/apache-camel-loop-does-not-stop-on-exception
https://issues.apache.org/jira/browse/CAMEL-8945
So, can't I continue after catching the exception in loop?
In my case, after catching the exception,
Incidentally, this is where a bit of my confusion lies:
to retrieve data from a web service,
read the response and pass the data to another application. (make a
request and get the response?) <*to *uri="http4://{{url}}"/>
it used to read from a database, but now needs *to get its input from t
Hi,
I doubt it is the FTP because I have also done a route with camel-ftp
inside docker and it worked fine to retrieve a file. If you enter the
docker container with bash, can you manually login to the ftp site and
download the file?
Best
Souciance
On Tue, Sep 27, 2016 at 11:09 PM, sparekh [via
By the way, which version of Camel are you using? And maybe I'm not quite
understanding what you're trying to do but it sound like you want to call *to
*an http endpoint and aren't waiting to receive from the endpoint.
On Tue, Sep 27, 2016 at 4:04 PM, jeffz wrote:
> I'm using Camel - through Se
If you put a log message right after the Netty call what does it show?
On Sep 27, 2016 4:04 PM, "jeffz" wrote:
> I'm using Camel - through ServiceMix - to retrieve data from a web service,
> read the response and pass the data to another application. This code was
> inherited, so much of the fr
Seeing a weird issue when trying to retrieve a file on a public FTP server
via the camel-ftp component. The camel route is running in a docker
container with openjdk:8-jdk image. The jar is built with dependencies and
runs correctly when executed on local OS.
>From the trace log I can see that Cam
You could send the incoming message off to another component(s) with their
own thread pools.
Also, is there anyway to upgrade your version of Camel? There's a newer
version of the Netty component released as of 2.14.
On Tue, Sep 27, 2016 at 1:20 AM, jshankarc wrote:
> Hi Tadayoshi,
>
> If we i
I'm using Camel - through ServiceMix - to retrieve data from a web service,
read the response and pass the data to another application. This code was
inherited, so much of the framework already exists. it used to read from a
database, but now needs to get its input from the web service response.
I have from defined as
ftp://?password=&fastExistsCheck=true&initialDelay=1000&delay=500&download=true&noop=true
&idempotent=true&idempotentKey=${file:onlyname}&idempotentRepository=#
&localWorkDirectory=/Users/**/temp/&include=aaa_bbb_\d+_\d{10}\.zip"
/>
I have files on ftp server n
@Sim
Also if you look a little farther down in the SEDA page you'll notice a
section called Use of Request/Reply.
On Tue, Sep 27, 2016 at 11:40 AM, sim085 wrote:
> Thanks :)
>
> I had a quick look at the seda component. I can see that it has a check on
> if the exchange is OutCapable or not.
Thanks :)
I had a quick look at the seda component. I can see that it has a check on
if the exchange is OutCapable or not. This returns true if ExchangePattern
is InOut.
So I think it is settled. It is up to the component to check the
ExchangePattern and act accordingly.
Claus Ibsen-2 wrote
>
See the seda option waitForTaskToComplete
On Tue, Sep 27, 2016 at 5:37 PM, sim085 wrote:
> This is getting confusing :(
>
> The docs for SEDA seem to say this should always be async.
> Link: http://camel.apache.org/seda.html
>
> They provide the following sample
>
> [code]
> public void configure
This is getting confusing :(
The docs for SEDA seem to say this should always be async.
Link: http://camel.apache.org/seda.html
They provide the following sample
[code]
public void configure() throws Exception {
from("direct:start")
// send it to the seda queue that is async
@sim
That's what I see as well. Which is why I decided to see if the short
circuit using inOnly to call the seda queue would change behavior and it
does.
On Tue, Sep 27, 2016 at 10:28 AM, Brad Johnson wrote:
> Going back to this unit test I added another route so I could comment it
> in or out
Going back to this unit test I added another route so I could comment it in
or out for different tests. If the inOnly is used to call the seda route
then it operates exactly the same regardless of whether the sendBody
(fire/forget) is used or the requestBody (request/reply) is used to
initiate the
@Ranx, I had another look at your code. I have changed the code a little and
ran the test again. From what I can see the SEDA endpoint acts correctly to
the InOut and InOnly ExchangePattern, i.e. - acts asynchronously when called
with InOnly and synchronously when called with InOut.
Changed code a
Hi,
I am testing with the kafka component, code is like
try {
camelContext.addRoutes(new RouteBuilder() {
public void configure() {
from("kafka:10.200.5.162:9092?topic=TMS_DATA&zookeeperHost=10.200.5.162&zo
sim085 wrote
> Just want to highlight that I have my reservations on point 3.
I assume you're right that it is the responsibility of each component to
read the MEP value and act on it if it needs to.
Point #4 says that the MEP indicator on the exchange will not impact some
routes.
In other word
Great .That worked :)
Are the headers from the JMS message that i am receiving being passed on to
the POST call as well? I thought only the relevant headers for http call
will be passed on.
--
View this message in context:
http://camel.465427.n5.nabble.com/Http-post-Request-returns-400-error
I'm not sure on point 3 either and the tests didn't appear that way. If
you look at the Unit test I posted earlier on that thread or even
copy/paste it into a test class and run it you'll notice that the sub-route
invocation behavior changes depending on whether the initial invocation of
the very
Excellent! Congratulations.
On Tue, Sep 27, 2016 at 1:18 AM, ncsibra wrote:
> Yes, changed the method call order. :D
> We are doing several weave* calls, just put a weaveById first, then it
> works
> fine.
> Actually, in our case, we have to put it last to be sure that our advice is
> the last(a
Hello,
Try to remove all readers and add just the content-type and method
.removeHeaders("*")
.setHeader(Exchange.CONTENT_TYPE,constant("application/json"))
.setHeader(Exchange.HTTP_METHOD, constant("POST"))
After that just see what header caused the problem and handle it somehow.
--
View th
Hello everyone,
I got a question regarding the Exchange.HTTP_QUERY of the http:component.
In which way should one provide the value ? Do the keys/values have to be
url encoded? Ive already noticed that spaces get encoded to %20. But
url-encoding would convert spaces to + (plus sign). So im confu
This is also my understanding and likewise I would like to know if this
interpretation is right or wrong.
That said, don't these points imply that the Exchange Pattern is a FLAG
which a target a end point can ignore or wrap logic around?
DariusX wrote
> 3. The MEP used for the "sub-route" deter
Just want to highlight that I have my reservations on point 3.
>From what I can see the ExchangePattern parameter doesn't determine
anything. The same applies for calling something using inOut or inOnly.
Again from what I can see from the examples I have tried out, what
determines if the paren
I have a camel route configured for reading from a JMS queue and POST it to a
service. My route is :
from("jms:queue")
.marshal()
.json(JsonLibrary.GSON)
.setHeader(Exchange.CONTENT_TYPE,constant("application/json"))
.setHeader(Exchange.HTTP_METHOD, constant("POST"))
.process(new Processor1())
.to
I found a solution. First overriding "isMockEndpointsAndSkip()" isn't working
at all (using every pattern including "jdbc:*"). Implementing an
AdviceRoutBuilder by my self is working:
But only by using weaveById. The interceptSend... is not working! Using
interceptSend... is showing a routedefin
Hello,
Are there any obstacles to creating a POJO producing class as a separate
artifact, and then putting it as a dependency in your pom file for your
Camel project?
What I mean is:
POJO producing class Eventbus writes and reads from ActiveMQ.
It has some methods to accepts parameters regarding
33 matches
Mail list logo
