d to cut the 3.20.8 release?
>
>Gregor
>
>On Mon, Oct 23, 2023 at 10:50 AM Benjamin Graf wrote:
>>
>> Hi,
>>
>> I'm actually working on CAMEL-20028, would be nice to have it in next 3.20.x
>> release. Need just this day to hopefully finish.
>>
Hi,
I'm actually working on CAMEL-20028, would be nice to have it in next
3.20.x release. Need just this day to hopefully finish.
Regards, Benjamin
On 23.10.2023 10:45, Claus Ibsen wrote:
Hi
And now the 3.20.x branch is ready also. Good luck Gregor.
On Mon, Oct 23, 2023 at 10:05 AM Claus I
Hi togehther,
I just created CAMEL-19967 as a possible regression to latest LTS versions
3.21.x and 4.0.x. Should maybe fixed before releasing another minor version,
but I'm fine if it is not concidered to block release process!
Regards,
Benjamin
On 09.10.23 10:56, Alexandre Gallice wrote:
Hi,
is there any reason why safeCopyProperties on Exchange are not
transferred to resulting exchange while aggregation? This way, objects
saved in AttachmentMessage are lost.
Regards,
Benjamin
OpenPGP_signature
Description: OpenPGP digital signature
Hi,
the latest refactorings of model structure elements name like
strategyRef to aggregationStrategy caused me a lot of headaches at
runtime because it seems that route definitions written in XML are not
validated against schema. I did a bit of debugging and pure code
analysis and can confirm
Hi,
try simple camel-mail component it should work corresponding to
(https://javaee.github.io/javamail/OAuth2)
Best regards
Benjamin
On 25.08.2022 11:21, Qianyan SUN wrote:
Hello,
Thanks for the response.
We have another question : if your team has the plan or is already developing
camel
:
Hi
The capability should be provided by the bundle. However as it’s not the case,
waiting improvement in Aries blueprint, the feature should provide it.
I will do it for 4.3.4 (the release will happen very soon).
Regards
JB
Le 6 oct. 2021 à 09:01, Benjamin Graf a écrit :
Hi,
I've a
:
>
> Hi
>
> The capability should be provided by the bundle. However as its not the
case, waiting improvement in Aries blueprint, the feature should provide it.
>
> I will do it for 4.3.4 (the release will happen very soon).
>
> Regards
> JB
>
>> Le
Hi,
I've a Karaf based distribution with bundles containing Camel routes
based on Aries blueprint. If I deploy them via deploy folder everything
works fine but via Karaf feature files I need to put a capability for
the Camel blueprint namespace to avoid resolve error on startup:
osgi.servic
On Wed, Jun 30, 2021 at 1:19 PM Benjamin Graf wrote:
>
> Hi Clause,
>
> please try the attached testcase with Camel 3.10 and 3.11 and you'll see
> that 3.11 fails for injected Endpoints. This test is for EndpointInject
> but it's the same for Produce. Everything is fin
of
https://issues.apache.org/jira/browse/CAMEL-16732 IMHO.
Regards
Benjamin
On 30.06.2021 10:27, Claus Ibsen wrote:
Hi
Can you tell us more details with some code sample of what you are
doing and where you think its not longer working as before?
On Tue, Jun 29, 2021 at 7:24 PM Benjamin Graf
Hi together,
can anybody confirm that DataSource autowire does not work anymore for
injected Endpoint/Producer since Camel 3.11 release. It seems the new
mechanism from core is not used if endpoint is not explicit part of a
route definition.
Regards
Benjamin
OpenPGP_signature
Descriptio
Sure, will open an issue ticket as I know now it is not intended! ;-)
On 06.04.2020 18:07, Andrea Cosentino wrote:
> Can you provide a reproducer of this?
>
> Il lun 6 apr 2020, 18:04 Benjamin Graf ha scritto:
>
>> Hi Claus,
>>
>> not anymore since commit "
04.2020 17:59, Claus Ibsen wrote:
> Hi
>
> It should have string parameters, where you can use {{foo}} as syntax
>
> On Mon, Apr 6, 2020 at 5:19 PM Benjamin Graf wrote:
>> Hi,
>>
>> is it intended that endpoint dsl does actually not support property
&g
Hi,
is it intended that endpoint dsl does actually not support property
placeholder resolving?
Regards,
Benjamin
signature.asc
Description: OpenPGP digital signature
his case.
>
> Thoughts?
>
> Il giorno gio 2 apr 2020 alle ore 16:49 Benjamin Graf
> ha scritto:
>
>> Hi together,
>>
>> I found a bug in 3.2.0 karaf feature for camel-xslt.
>>
>> is: mvn:org.apache.camel/camel-commands-core/3.2.0
>>
>> should b
Hi together,
I found a bug in 3.2.0 karaf feature for camel-xslt.
is: mvn:org.apache.camel/camel-commands-core/3.2.0
should be:
mvn:org.apache.camel.*karaf*/camel-commands-core/3.2.0
Regards
Benjamin
On 02.04.2020 15:48, Francois Papon wrote:
> +1 (non-binding)
>
> Thanks guys for the great j
Hi,
has anybody seen any 3.0.1 artifacts on official maven central
"https://repo.maven.org/maven2"; not only
"https://repo1.maven.org/maven2";. I have this behavior also for latest
released Apache Artemis artifacts. :-(
Regards
Benjamin
On 17.01.2020 08:34, Andrea Cosentino wrote:
> Gregor, goo
Hi
BTW why is hawtio a problem for Camel for political reason? It is yet the
official front end for ActiveMQ. Is this seen different in different Apache
projects???
Best regards
Benjamin
On 01.12.2013 17:58, Babak Vahdat wrote:
> Hi
>
> Let me sincerly tell you my personal opinion. To me the vet
implementation but I believe the changes would be very
> extensive and make it difficult to, if not eliminate, the ability to
> support the extensions that both implementations provide that our users
> depend on.
>
> Just my two cents...
>
>
>
> On Sun, Dec 2, 2012 at 4:12 AM
; On Tue, Nov 6, 2012 at 3:31 PM, Scott England-Sullivan
>> wrote:
>>> If nobody has an issue with it I am proceeding with option 3.
>>>
>>> Any concerns?
>>>
>>> On Mon, Nov 5, 2012 at 3:02 PM, Benjamin Graf
>> wrote:
>>>> Hi Sco
On Tuesday, November 6, 2012 at 10:31 PM, Scott England-Sullivan wrote:
>
> > If nobody has an issue with it I am proceeding with option 3.
> >
> > Any concerns?
> >
> > On Mon, Nov 5, 2012 at 3:02 PM, Benjamin Graf (mailto:benjamin.g...@gmx.net)> wrote:
36 PM, Benjamin Graf wrote:
Hi,
I would recommend Option 3a with an additional rename of camel-blueprint
component to camel-aries-blueprint just to be clean and avoid any further
friction.
Btw. which breaking backwards compatibilities did you find with Spring DM
and
Gemini Blueprint in Option 1 Cons? I d
Hi,
I would recommend Option 3a with an additional rename of camel-blueprint
component to camel-aries-blueprint just to be clean and avoid any further
friction.
Btw. which breaking backwards compatibilities did you find with Spring DM and
Gemini Blueprint in Option 1 Cons? I didn't find any whil
use
camel-spring and any gemini blueprint camel component together since you will
have to install two OSGi handlers to fulfill dependencies.
> Best Regards,
> Scott ES
>
>
> On Fri, Oct 12, 2012 at 9:42 AM, Benjamin Graf
> wrote:
> > By the way. Any more comments o
r Camel 3.0?
>>>>
>>>> Best Regards,
>>>> Scott ES
>>>>
>>>> On Oct 11, 2012, at 8:42 AM, Willem jiang (mailto:willem.ji...@gmail.com)> wrote:
>>>>
>>>>> FYI, Aries Blueprint 1.0 was released.
gt;Weibo: willemjiang
>
>
>
>
>
>On Thursday, October 11, 2012 at 1:10 PM, Benjamin Graf wrote:
>
>> Hi Christian,
>>
>> the issue is that Gemini has a different packaging and camel spring
>has a dependency which tries to load classes from spring OSGi whe
27;m
>right?
>In this case, I don't understand what the issue is?
>
>Best,
>Christian
>
>On Wed, Oct 10, 2012 at 12:53 PM, Benjamin Graf
>wrote:
>
>> Hi everybody,
>>
>> I tried to implement a new camel component for gemini-blueprint. It
>seems
&
.
Any suggestions?
Benjamin
Original-Nachricht
> Datum: Tue, 09 Oct 2012 11:19:36 +0200
> Von: "Benjamin Graf"
> An: dev@camel.apache.org
> Betreff: Re: Dependencies of camel-spring
> I give it a try it's two changed imports and one dependeny chang
Oct 2012 11:03:50 +0200
> Von: Claus Ibsen
> An: dev@camel.apache.org
> Betreff: Re: Dependencies of camel-spring
> On Tue, Oct 9, 2012 at 10:08 AM, Benjamin Graf
> wrote:
> > Hi,
> >
> > does anybody knows why camel-spring still depends on spring-osgi? This
&g
Von: Claus Ibsen
> An: dev@camel.apache.org
> Betreff: Re: Dependencies of camel-spring
> On Tue, Oct 9, 2012 at 10:08 AM, Benjamin Graf
> wrote:
> > Hi,
> >
> > does anybody knows why camel-spring still depends on spring-osgi? This
> bundle is gemini-blueprint since
e and not Camel. Because JBoss module loader tries
> > to load the classes from the org.apache.camel.osgi package which is
> > optional, and only in use for OSGi runtimes.
> >
> >
> > On Tue, Oct 9, 2012 at 10:28 AM, Benjamin Graf
> > wrote:
> > > Well, lo
Ibsen
> An: dev@camel.apache.org
> Betreff: Re: Dependencies of camel-spring
> This is a JBoss issue and not Camel. Because JBoss module loader tries
> to load the classes from the org.apache.camel.osgi package which is
> optional, and only in use for OSGi runtimes.
>
>
> On Tue
.java:120)
... 14 more
Original-Nachricht
> Datum: Tue, 9 Oct 2012 10:13:04 +0200
> Von: Claus Ibsen
> An: dev@camel.apache.org
> Betreff: Re: Dependencies of camel-spring
> On Tue, Oct 9, 2012 at 10:08 AM, Benjamin Graf
> wrote:
> > Hi,
> >
> >
Hi,
does anybody knows why camel-spring still depends on spring-osgi? This bundle
is gemini-blueprint since 2009 and won't be developed anymore. This fact forces
to use an old unsupported bundle if you like camel with spring and OSGi. :-( I
think it should change whether to create a new camel-g
istian
>
> On Tue, Sep 4, 2012 at 8:41 AM, Benjamin Graf wrote:
>
>> Hi,
>>
>> I got no feedback to this issue, yet. Any suggestions?
>>
>> Benjamin
>>
>> Original Message Subject: Issue with JndiContext in
>> came
Hi,
I got no feedback to this issue, yet. Any suggestions?
Benjamin
Original Message
Subject:Issue with JndiContext in camel tests
Date: Tue, 21 Aug 2012 21:18:18 +0200
From: Benjamin Graf
Reply-To: dev@camel.apache.org
To: dev@camel.apache.org
Hi,
I
Hi,
I had a lot of troubles with JndiContext in camel junit tests. I recognized that
if you configure the jndiregistry in the unit test produced by
CamelInitialContextFactory you'll always will get a new one if any library in
between with do a new InitialContext() call. Thats why I created a simpl
38 matches
Mail list logo
