Hi,
Thank you for the answer!
The way the API is consumed is via a payload in which you need to set an
offset and pagesize. So it's an iteration of HTTP POST calls with a
different payload
Don't know if this could help to specify which pattern / approach is the
best to follow in this case?
Hi
Okay so that is not a responsibility of the consumer / bridge error
handler if the error happens outside, eg in this case in the producer
(to).
So in that case you can use Camel's regular error handler which ought
to catch the write permission error and route it elsewhere.
However if you say
Hi Tom,
You can also use a poll enricher with a aggregation.
All depends about the trigger to call the webservice.
Regards
JB
On 16/10/2019 16:52, Tom Coudyzer wrote:
> Hi,
>
> I just started on learning Apache Camel, so please forgive me my basic
> questions.
>
> I'm having a webservice
OK, I read it and understand it a little more. Still it's not exactly what
I expected. An example I need to send a file with FTP component:
Source (SFTP Server) --> Camel --> Destination (FTPS Server)
As long as the file is at the source (and Camel is polling for whatever
reason) I don't need a
Hi,
I just started on learning Apache Camel, so please forgive me my basic
questions.
I'm having a webservice called via POST having a payload with paging
information in it.
What is the best way currently in Camel to produce an output which contains
the consolidated values from the calls.
I
No. I think it's
11.4.8 Bridging the consumer with Camel’s error handler
But unfortunately it doesn't help me with my case.
regards
Daniel
Von: ski n
Gesendet: Mittwoch, 16. Oktober 2019 16:16:52
An: users@camel.apache.org
Betreff: Re: BridgeErrorHandler on
Of course, I had CiA2 already opened.
Do you mean 11.5 (Example that bridges the consumer with Camel’s error
handler). There the bridgeerrorhandler is explained, but I'm not sure about
the reasons.
Op wo 16 okt. 2019 om 15:55 schreef Claus Ibsen :
> Hi
>
> If you have a copy of the CiA2 book
Hi
If you have a copy of the CiA2 book then read the error handler
chapter which details about the bridge error handler and the reasons.
On Wed, Oct 16, 2019 at 3:51 PM ski n wrote:
>
> Just note that SJMS component (=JMS 1.1) and SJMS2 component (=JMS 2.0).
>
> I also wonder why the default
Just note that SJMS component (=JMS 1.1) and SJMS2 component (=JMS 2.0).
I also wonder why the default for the bridgeErrorHandler option is false?
How can it set to true for all components globally? Or does it needs to be
set for each component like in this question:
Hi Karsten,
thanks for the swift reply!
How would we setup this "property auto reload" feature?
And why would it restart the existing context?
Can it also just restart the affected routes?
Regards,
Ralf
On 10/16/19 10:43 AM, Karsten Blume wrote:
Hello Ralf,
Use property placeholder for your
Hi guys,
thanks for the answers. In the meantime I tried with Camel 2.24.2 and the
JMS-Component but the problem is still the same.
Next I will with the sjms2 component.
I think that in the JMS-Component the EndpointMessageListener could do more
with the exception as just setting it into
@Daniel instead of camel-jms you can also try camel-sjms (The Simple (or
Springless) JMS component). In my experience this component works better.
Op wo 16 okt. 2019 om 12:56 schreef Claus Ibsen :
> Hi
>
> The bridge cannot do 100% of all errors as its how the underlying
> library is designed.
Hi
The bridge cannot do 100% of all errors as its how the underlying
library is designed. camel-jms uses spring jms and it has some
"limitations" on how it works and handle errors, where it does
re-connection and whatnot with the connection pool.
On Wed, Oct 16, 2019 at 10:21 AM wrote:
>
> Hi
Hi
Same as with jms, but you have to provide more details what your
use-case and error is and whether the bridge can react or not.
And also try with newer version, and see this page for support/help:
https://camel.apache.org/community/support/
On Wed, Oct 16, 2019 at 10:52 AM ski n wrote:
>
> I
That's good to know because I also have other Camel Routes which use SFTP as
consuming endpoint.
I will check their behaviour too.
Regards,
Daniel
Von: ski n
Gesendet: Mittwoch, 16. Oktober 2019 10:51:48
An: users@camel.apache.org
Betreff: Re:
I have the same issue on SFTP with bridgeErrorHandler=true. I expected that
in case of an error not only an exception is thrown, but the message is
handled by the defaultErrorHandler or deadLetterChannel (for example the
message however doesn't arrive on the deadLetterChannel in case of an
Hello Ralf,
Use property placeholder for your endpoints, define the property configuration
as automatically reloadable and change the URI by kafka cmd line, config file
in etc/ or by JMX.
The context is restarted automatically after URI change.
The property should be changeable also
Hi guys,
I tried to use the bridgeErrorHandler flag on my JMS Endpoint but sadly it does
not work.
Because there is a lot of code which I have to share with you to make you
understand my problem I created a stackoverflow question as it is way easier to
read and to respond on comments there.
Hi Ralf,
If you have these routes as a RouteBuilder beans, I think you can utilize
CamelContext APIs such `addRoute` to add the bean dynamically. Of course
you will need to implement a way to hot reloading of your .class files
whenever you deem to. You can take a look at this test for an example:
Hello all,
is there a way to restart defined routes so that the from() URI gets
updated?
We have tried several things using the "Controlbus" component, but we
cannot restart a defined and running route /with changed URI parameters/.
Background (what do we want to achieve):
We have
20 matches
Mail list logo
