Hi
Ah okay, then yeah then its possible not supported. You are welcome to
take a look at the source code and see if you can modify the regex to
support dash.
We love contributions
http://camel.apache.org/contributing
On Tue, Jul 3, 2018 at 9:46 PM, bukaj_s wrote:
> I am sorry I wrote all
The Camel community announces the immediate availability of Camel
2.22.0. This release contains 216 fixes and improvements committed in
the past few weeks. This release also introduces Spring Boot 2.0
support.
The artifacts are published and ready for you to download [1] either
from the Apache
Just wondering if anyone else has experienced this? For now we have
reverted back to Camel 2.19.5
On Wed, Jun 20, 2018 at 10:37 PM Kartik wrote:
>
> There appears to be a regression between Camel 2.19.5 and Camel 2.20.1
> where if maximumRedeliveries is set, nothing is traced.
>
>
I am sorry I wrote all messages in context of camel-sql and forgot to
mention it. As far as I understand named parameter's regex doesn't take
into account dashes in named parameters for sql prepared statement. My
questions is if this is correct observation and why is that. If I want to
use values
Multiple CamelContexts in spring boot is NOT supported, its by design
to have 1 camel context only.
If the NPE is fixed then you may hit further problems down the line as
the bean post processor have not camel context injected as it ought to
have.
You are welcome to try to patch a local source
Hi
Ah okay, good to hear you were able to build a better solution that runs stable.
There are a lot of Camel applications over the world running stable in
production, so if we hear about memory leaks, we are keen on fixing /
looking into them.
But as you say they can sometimes be hard to track,
Hi Claus,
thanks for your help. Unfortunately, the data with which I work are secret, and
so is the connection to our data provider. For that reason, it might be tough
to construct a reproducible example.
In the meantime, I threw my project into the waste and re-developed it from the
scratch.
Hi
What version of Camel do you use?
And are you always using temporary "private" dynamic queues for
request/reply schenarious? Isnt there an overhead of some sorts on rabbitmq
side if you need to have a new queue per message?
Well regardless if that is a common practice, we can look into a way
Hi
Use # syntax, see for example the unit test class
SqlProducerAlwaysPopulateStatementTest
On Sun, Jul 1, 2018 at 3:51 PM, bukaj_s wrote:
> Hello.
> How can one plug in his own implementation of prepareStatementStrategy?
> Using prepareStatementStrategy=com.example.CustomStrategy is not
Hi
Can you tell a bit more where you use those headers? Camel has no
restrictions on header names. Its the protocol of the components that
may have such as JMS, HTTP etc.
On Sun, Jul 1, 2018 at 3:36 PM, bukaj_s wrote:
> Hello.
> Am I correct if I say we cannot have dashes in named parameters?
>
Hi
Thanks for reporting and the PR
https://github.com/apache/camel/pull/2403
On Thu, Jun 28, 2018 at 8:13 PM, Darrell King wrote:
> Hi
>
> I'm using camel-rabbit 2.21.1 and want to
> create an exclusive consumer. I've tried using the exclusive=true
> option but that creates an exclusive queue
Hi
If its a SOAP Fault then its not the same as an exception, and
therefore not captured in that statistics.
There is an option on camel to transform SOAP faults to exception with
handleFault=true
On Thu, Jun 28, 2018 at 4:20 PM, Martin Pelikán wrote:
> Hello,
>
> I have a problem with route
Hi
Its a bit hard to help when there is no more details about Camel and
what Camel routes you have etc.
Maybe you can build a sample project that can be used to demonstrate /
reproduce the issue you see.
Also there is some tips on support here in the bulleted list
Hi
Camel uses swagger to generate the json file, and its tied to be
Swagger 2.0 spec with the version of swagger we use.
To support 3.0 we would need to upgrade the swagger library, and
potential do migration as its potentially not a drop in replacement.
I logged a ticket so support 3.0 spec in
14 matches
Mail list logo