Nevermind, I have the solution.
My issue was a missing spring bean of type
'PropertySourcesPlaceholderConfigurer' that would then be able to use the
property sources defined with the @TestPropertySource annotation.
The code change:
Add ' PropertySourcesPlaceholderConfigurer.class' to
@Context
I am using the camel cxf component to connect to a partner website.
The partner website requires timestamp security below is my endpoint
configuration. About 25-50% of the time I am receiving a
Incorrect Timestamp (from Client)
According the partner this is because the time on the s
Kia ora,
I'm having an issue writing a camel-spring-javaconfig test of a camel route
where the RouteBuilder bean relies on Spring to inject fields annotated with
@Value.
This repo: https://github.com/bedebignell/camel-bug-repro/ is able to reproduce
the error by running 'mvn test
-Dtest=nz.bi
On Tue, Dec 15, 2020 at 5:40 PM Ajmera, Hemang C wrote:
>
>
> Hi
>My understanding was that LTS version will be supported for 1 year. So
> even if 3.7 is release version 3.4 will be continued to be supported for bugs
> and security fixes. Did I misunderstood something?
>
Yes each LTS has 1
3.4.x will be supported as lts for one year from the release date of 3.4.0
Inviato da Yahoo Mail su Android
Il mar, 15 dic, 2020 alle 17:40, Ajmera, Hemang C ha
scritto:
Hi
My understanding was that LTS version will be supported for 1 year. So even
if 3.7 is release version 3.4 will be
Hi
My understanding was that LTS version will be supported for 1 year. So even
if 3.7 is release version 3.4 will be continued to be supported for bugs and
security fixes. Did I misunderstood something?
This is the reference
https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/
Than
Hi
For Camel 2.x at this moment then Camel 2.25.x is the only supported
release. We only do patch releases, and there are no new minor
releases (eg 2.26) planned. Camel 2.x is very likely to be EOL by the
end of 2021, and we mainly only at this time put effort into security
fixes. The 2.x is not a
Hi Symphoni,
I wonder where you found the owner mail alias? Moving the conversation
to the users mailing list.
I'll try to answer to the best of my abilities, others may correct me.
Answer differs slightly based on the major version (2.x or 3.x). For
2.x we supported the latest two releases. Sinc
Ad 1)
Its the new endpoint-dsl. Those expressions will be like that. Using
getUri is a workaround but not ideal.
We can see if we can improve this in camel-management. You are welcome
to create a JIRA about this.
Ad 2)
Yeah that too is a little bug. You can do a PR to implement and
return true
Sorry, I forgot this...
I'm using Camel 3.6.0, and my tests are with an IDE using camel-main.
Regards,
Nicolas
-Message d'origine-
De : Jean-Baptiste Onofre
Envoyé : mardi 15 décembre 2020 08:54
À : users@camel.apache.org
Objet : Re: JMX issues with processor
Hi Nicolas,
Which camel
+1 Tadayoshi, folk seem to use the Maven repository far more than
downloading a ZIP/tar.gz archive, I can't actually fathom how a
ZIP/tar.gz with binary jars is useful as we don't provide a
ZIP/tar.gz+dependencies variant, so for any binary jar we produce one
has to go and download a non trivial nu
11 matches
Mail list logo
