On Fri, Aug 19, 2016 at 3:54 PM, Claus Ibsen wrote:
> There is already CI jobs for this - they are the ones named notest,
> which ought to be configured to publish to staging m2 repo after
> success:
> https://builds.apache.org/view/A-D/view/Camel/
>
If I switch the current version to 2.18.0-SN
publish nightlies of the tips of
the actively maintained release lines (2.18.x, 2.17.x, 2.16.x) to the
snapshots repo under 2.18-SNAPSHOT & co.
WYDT?
Cheers.
On 19 Aug 2016 14:32, "Claus Ibsen" wrote:
> On Wed, Aug 17, 2016 at 4:12 PM, Raul Kripalani wrote:
> > Hi
Hi Claus,
Any further thoughts?
This is becoming an ongoing problem in my projects and I'd appreciate your
views before making any changes.
Cheers!
On 17 Aug 2016 15:22, "Raul Kripalani" wrote:
> Also Claus, I found a mixture of per-release-line SNAPSHOTS and
> per-rel
t.com/?utm_source=email&utm_medium=email&utm_campaign=evosent_raul>
| blog: raul.io
<http://raul.io?utm_source=email&utm_medium=email&utm_campaign=evosent_raul>
|
skype: raul.fuse
On Wed, Aug 17, 2016 at 3:12 PM, Raul Kripalani wrote:
> Hi Claus,
>
> I see
.2-SNAPSHOT is a pain to
> work with, and having to prune/remove old versions becomes a
> maintenance problem.
>
> Using -SNAPSHOT then its easy to be assure its using the latest code
> on that branch, which is the intension of the SNAPSHOT.
>
> On Wed, Aug 17, 2016 at 9:35 AM, Ra
wards.
I assume its "just" a matter when the RC is cut then the version
number typed for the Maven command should be 2.18.0 instead of 2.18 in
these situations.
On Wed, Aug 17, 2016 at 1:01 AM, Raul Kripalani wrote:
> Hi all,
>
> I've come across an obscure bug using
Hi all,
I've come across an obscure bug using the karaf-maven-plugin to package a
custom Karaf distro containing Camel 2.18-SNAPSHOT.
Karaf expects feature version numbers to match the same format as OSGi
versions [1]. OSGi versions **require** a micro component.
Karaf uses the Felix org.apache.
On Wed, Apr 6, 2016 at 4:35 PM, Quinn Stevenson wrote:
> Also, since Camel doesn’t really “release” any SNAPSHOT builds, this is a
> decision that only effects the development community IMO. People
> building/using SNAPSHOT versions must understand what’s going on anyway -
> either way will work
During a discussion in the Camel dev@ list about possibly adopting the
bnd-maven-plugin, a contributor noticed differences in the way that package
export versions are computed between Felix' maven-bundle-plugin and the
former.
http://camel.465427.n5.nabble.com/DISCUSS-Moving-from-maven-bundle-plug
On Wed, Apr 6, 2016 at 12:29 AM, David Jencks <
david_jen...@yahoo.com.invalid> wrote:
> I don’t know how camel is doing release versions after a period of
> development, but recall that osgi version 1.2.3.SNAPSHOT is after 1.2.3, so
> if you use normal maven release practices and version the expo
I agree with you guys. I have doubts whether going the bnd-maven-plugin
brings in any actual benefits vs our current setup.
Now that we use the "lightweight" process anyway (no 'bundle' extensions,
just generating the manifest), both approaches got to be functionally
equivalent, aside from minor d
On Tue, Apr 5, 2016 at 11:00 PM, Matt Pavlovich wrote:
> I was ruminating about this as well-- I agree its not exact; however, is
> there any real impact? The bundle version is indicated by the SNAPSHOT.
> How would the package export having the .SNAPSHOT qualifier (which would
> not impact any
aulvk>
On Tue, Apr 5, 2016 at 10:45 PM, Raul Kripalani wrote:
>
> On Tue, Apr 5, 2016 at 7:58 PM, Quinn Stevenson <
> qu...@pronoia-solutions.com> wrote:
>
>> Do we need to keep the “.SNAPSHOT” in the exported package versions?
>
>
> Does the bnd-maven-plugin f
On Tue, Apr 5, 2016 at 7:58 PM, Quinn Stevenson wrote:
> Do we need to keep the “.SNAPSHOT” in the exported package versions?
Does the bnd-maven-plugin feed back the calculated version into the build,
perhaps as a property? We need to inject the correct version number
downstream in the Karaf fe
That was my exact same thought when I took a stab at the camel-hystrix
component myself:
https://github.com/apache/camel/commits/feature/camel-hystrix.
For me, Hystrix is not an endpoint but a mechanism to deal with failure, no
matter if thrown by an endpoint, a processor, or any other element of
On Mon, Apr 4, 2016 at 4:44 PM, Matt Pavlovich wrote:
> The current website looks the same as it did when it was created:
>>
>> https://web.archive.org/web/20070701184530/http://activemq.apache.org/camel/
>>
> I thought the Karaf guys did a nice job on the website re-work. Is there a
> new base f
It's defined by the clean goal of the bundle plugin. Check out the
definition in the parent pom.
Raúl.
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
Blog: raul.io | twitter: @raulvk <https://twitter.com/raulvk>
On Wed, Mar 30, 2016 at 7:00 PM, Claus Ibsen wrote:
> On Wed, Mar 30, 2016 at 5:12 PM, Raul Kripalani wrote:
> > Yep, today, hopefully.
> >
>
29, 2016, at 9:59 AM, Claus Ibsen <mailto:claus.ib...@gmail.com>> wrote:
> >>
> >> On Tue, Mar 29, 2016 at 4:27 PM, Raul Kripalani <mailto:ra...@apache.org>> wrote:
> >>> On Tue, Mar 29, 2016 at 6:21 AM, Claus Ibsen <mailto:claus.ib...@gmail.
On Tue, Mar 29, 2016 at 2:27 PM, Quinn Stevenson <
qu...@pronoia-solutions.com> wrote:
> I was able to get the bnd-maven-plugin working with camel-core last night
> on the jdk8-lambda branch. I still need to finish the bnd.bnd
> configuration file to make the manifests match, but I’m getting clos
On Tue, Mar 29, 2016 at 6:21 AM, Claus Ibsen wrote:
> Can we flip the switch so you have to enable it on the maven modules
> that you want to be an osgi bundle. I am asking because people who are
> not using OSGi should really not see camel.osgi.skip=true in the
> examples / camel-spring-boot-sta
Camel riders,
I'm seeing an issue caused by the MulticastProcessor not handling async
routing end-to-end. It does use its own threadpool to process its routing
tasks, as well as to perform the aggregation (on-the-fly).
However, during all that time, the calling thread is blocked waiting for
the m
;> the -notest also publish the SNAPSHOT to the snapshot mvn repo, so the
> >> CI jobs can pickup these new JARs.
> >>
> >> If we get that more reliable then Camel end users can also easier use
> >> SNAPSHOT instead of having to build locally to be sure they
> configured somehow so the generated MANIFEST.MF is not replace so end
> users do not need to do anything with a JAR plugin?
>
>
>
>
>
> On Sat, Mar 26, 2016 at 1:09 AM, Raul Kripalani wrote:
> > There is good news, bad news, and good news again ;-)
> >
> &
There is good news, bad news, and good news again ;-)
*Good news:* Now that Camel 2.18 is officially on JDK8, we can use lambdas
in our code. Woohoo!
*Bad news:* Our current Maven build breaks when doing so.
This is what happens:
1. maven-bundle-plugin version 2.3.x cannot parse JDK8 lambdas
Hey Guru,
Nice ideas! Some thoughts inline.
Cheers,
Raúl.
On Thu, Mar 24, 2016 at 12:12 PM, Gnanaguru S wrote:
>
> Guys,
>
> These are some of the feature, I wish to see in upcoming camel versions. It
> would be useful to have.
>
> 1. Timeout option in a internal synchronous endpoint - we very
On Thu, Mar 24, 2016 at 8:55 PM, Claus Ibsen wrote:
> There has been a camel-rx component for several years now, but nobody
> has shown interest in it. Nor is people screaming in this community
> about reactive libraries. In fact people rely on Camel being "not in
> the forefront"
>
A camel-rx c
On Thu, Mar 24, 2016 at 5:24 PM, Krzysztof Sobkowiak <
krzys.sobkow...@gmail.com> wrote:
> I think, the way to Camel 3 should also include the renovation of the Core
> (if really necessary) or even rewriting and
> making it more asynchronous, e.g. using rx.java (the later can be
> eventually part
Yep. What Claus proposes sounds sensible.
– Raúl.
On Thu, Jan 28, 2016 at 6:13 PM, Claus Ibsen wrote:
> On Thu, Jan 28, 2016 at 3:48 PM, James Carman
> wrote:
> > I would rather us bump the major version number if we're going to start
> > requiring users to use Java8.
> >
>
> Yeah that was als
On Thu, Jan 28, 2016 at 3:55 PM, Johan Edstrom wrote:
> If we start using say Lambdas, then you are SOL on Java 7.
>
> Right?
>
What I'm saying is that us moving to JDK8 doesn't/shouldn't break any
aspect of the public API we (Camel) expose to our consumers:
> Major version X (X.y.z | X > 0) MU
On Thu, Jan 28, 2016 at 3:49 PM, Johan Edstrom wrote:
> Well - that doesn’t hold true for Java8 language features, does it?
>
Which part, Johan?
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://w
Good point, James. But after spending over 6 years in 2.x, I think users
might expect a little more from 3.x than just a standard 2.x release + JDK
upgrade. So from the public view standpoint, I'm not so sure.
Also, JDK8 is backwards compatible with JDK7, so according to Semver a
major version inc
We would need to upgrade Camel 2.17 to work with, at least, Karaf 3.x. The
first version supporting JDK8. Ideally, we should upgrade to Karaf 4.0.0.
In fact, I think it already works with Karaf 4.0.0, but we need to state it
officially.
https://camel.apache.org/karaf.html
As long as there are JD
On Thu, Jan 28, 2016 at 2:20 PM, David Karlsen
wrote:
> Just a fyi. I think archaius is gone in Hystrix 1.5 (configuration is an
> interface with default imp with archaius). There is a RC out of Hystrix 1.5
>
Cool, thanks for the heads-up, David!
*Raúl Kripalani*
PMC & Committer @ Apache Ignite
LOL. No worries, Claus! And thanks for informing.
When I saw your massive pic yesterday on the frontpage I thought: "well,
that's an embarrassing CSS styling #fail". It didn't even cross my mind it
might have been intentional. So, easy, I think you have a pretty good
standing in the community!
Th
anually, seems too much work to me. I believe all that can be
> expressed through a regular component.
>
> Not sure way would be the better approach going forward. May be we can
> merge both approaches and offer the regular URI based component usage
> and also the additional fluent AP
+1 (binding)
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Sat, Oct 24, 2015 at 10:44 AM, Gregor Zurowski
wrote:
+1
On 5 Oct 2015 19:21, "Daniel Kulp" wrote:
>
> This is a vote to release Apache Camel 2.16.0. There was a TON of work
> done over the last 6 months to get this ready so it’s time to get it out.
>
> Tag:
>
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=cad9dc2be555b7460e141fde58
+1
On 30 Sep 2015 02:26, "Daniel Kulp" wrote:
> This is a vote to release Apache Camel 2.16.0. There was a TON of work
> done over the last 6 months to get this ready so it’s time to get it out.
>
> Tag:
>
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=a9ddbc94874817ab4b6e21bab60
Hey,
Are you using ActiveMQ as a broker? If yes, have you enabled prioritized
messages broker-side?
http://activemq.apache.org/how-can-i-support-priority-queues.html
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://ab
on of keeping a good uptime on the service in my
> > opinion it is not that big a deal
> > where or what is hosting it. The important thing is that we get this up
> > read-write ASAP.
> >
> >
> > Just my $0.02
> > // Pontus
> >
> >
Hey Charles,
Done. I also fixed some checkstyle and updated the fix versions in the JIRA
ticket.
Regards,
Raúl.
On Sun, Sep 13, 2015 at 5:06 PM, Charles Moulliard wrote:
> Hi,
>
> Can somebody helps me to also apply this change to camel 2.15.x branch (
> https://issues.apache.org/jira/browse/C
:%s/camel-tarball/camel-tarfile
On Sat, Sep 12, 2015 at 4:38 PM, Raul Kripalani wrote:
> Hey Claus,
>
> Agree. I hope I can finish my work on the camel-hystrix component so that
> it's available for 2.16.0 at least without OSGi support (initially), as
> this depends on poss
Hey Claus,
Agree. I hope I can finish my work on the camel-hystrix component so that
it's available for 2.16.0 at least without OSGi support (initially), as
this depends on possible SMX bundles and can be added in micro versions.
On the other hand, I applied a patch with a camel-tarball component
gt;>>
> >>> It's even worse than what I thought because after the Gimp people told
> SF
> >>> to stop doing their shady things, they actually insisted during 2015:
> >>>
> >>
> https://mail.gnome.org/archives/gimp-developer-list/2015-May/msg00
Sergey,
Done.
Cheers,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Fri, Aug 28, 2015 at 5:11 PM, Sergey Beryoz
Hi team,
Our tests are taking around 4 - 5 hours to execute on Jenkins CI.
I think we can reduce this time by making use of the maven-surefire-plugin
parallelisation [1]. Not sure if the partitioning is able to span tests in
multiple projects, though. I've used it in the context of a single Maven
Hi team,
Hystrix [1] is a powerful toolbox framework based on RxJava for building
JVM-based fault-tolerant distributed systems, made OSS by Netflix.
Due to the nature of Camel, our users inherently deal with distributed
systems and therefore I thought integrating this framework into Camel would
b
+1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Mon, Aug 17, 2015 at 1:23 PM, Daniel Kulp wrote:
>
>
> This i
Hey Dan,
Unfortunately the pom version number is incorrect, says 2.15.4.
It looks like the previous take was not rolled back entirely.
Regards,
Raúl.
On 15 Aug 2015 19:22, "Daniel Kulp" wrote:
> This is a vote to release Apache Camel 2.15.3. It’s been quite a while
> since 2.15.2 and with lo
ber & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Fri, Aug 14, 2015 at 7:02 PM, Raul Kripalani wrote:
> Pushed fix for camel-sip. It turns ou
Pushed fix for camel-sip. It turns out that the referenced Java SIP specs
bundle was not exporting any packages, hence leading to the resolution
issue.
As far as I'm concerned, you can cut the new RC, Dan.
Raúl.
On Fri, Aug 14, 2015 at 6:44 PM, Raul Kripalani wrote:
> Had a quick loo
Had a quick look at the failures, and I was able to fix camel-sip. Pushing
soon.
Was not able to reproduce camel-hazelcast and camel-vertx; must've been a
coexistence issue with another feature.
Please wait until you see my push to cut the new RC.
Regards,
*Raúl Kripalani*
Apache Camel PMC Memb
if you edit the jre.properties to
> stick the javax.activation to version 1.0 this will be OK.
>
> camel-jetty9 will never work on Karaf 2.x (or 3.x) as those versions of
> Karaf are based on Jetty 8.
>
> Dan
>
>
>
> > On Aug 13, 2015, at 2:06 PM, Raul Kripalani wrot
Tried installing all features in Karaf 2.4.3 with the following ones
failing (legend for symbol in brackets below):
* (!) camel-avro
* (c) camel-cxf (only in presence of some other feature I haven't
determined - ok when installed on an empty container)
* (!) camel-hazelcast
* (!) camel-hbase
* (!)
kripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Aug 13, 2015 at 5:22 PM, Raul Kripalani wrote:
> Hey guys,
>
> I'm helping out the colleagues at Apache Ignite set up their Github
> integration similar to what we have here at Camel [1].
>
> ASF Infra said the follo
Hey guys,
I'm helping out the colleagues at Apache Ignite set up their Github
integration similar to what we have here at Camel [1].
ASF Infra said the following in the ticket:
> As far as I can tell, Camel has GitHub integration setup for their
svn->git mirror.
Is it true that we still have a
he email thread you
> initiate will be the most popular in years :-)
>
> Sergey
>
> On 17/04/15 11:13, Raul Kripalani wrote:
>
>> Just found this marketing landing page published on social networks. It's
>> made by TIBCO and attempts to highlight the downsides o
Just found this marketing landing page published on social networks. It's
made by TIBCO and attempts to highlight the downsides of Open Source ESBs.
You don't need to be a rocket scientist to gather what exact ESB they are
targeting (not us): just look at the images.
http://www.tibco.com/integrati
My +1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Wed, Mar 4, 2015 at 6:58 AM, Willem Jiang wrote:
>
> This
Thanks for taking care of this!
On Wed, Sep 10, 2014 at 2:57 AM, wrote:
> Repository: camel
> Updated Branches:
> refs/heads/master 734afce69 -> 19b2aa315
>
>
> CAMEL-7795 Fixed the regression of MDCResetTest
>
>
> Project: http://git-wip-us.apache.org/repos/asf/camel/repo
> Commit: http://git
I'm about to push a change to the MDC UoW, and perhaps another one to the
log endpoint.
Hopefully sometime today ;-)
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in
p://blog.raulkr.net | twitter: @raulvk
On Thu, Jul 24, 2014 at 3:00 PM, Claus Ibsen wrote:
> Hi
>
> Anyone able to see those images? Maybe you can log a JIRA and attach the
> images there. Not sure if this mailing list accepts images and embedded
> files in mails etc.
>
>
>
Team,
We just had an OOM incident in our dev environments after upgrading from
Camel 2.10.3 to 2.13.1. Heap settings have remained untouched.
A heap dump showed millions of DefaultMessageHistory instances retained
(see screenshot), along with their corresponding Date and StopWatch
instances. Obvi
we would
> need for this change, so technically the way is open for backporting the
> fix, see also this commit:
>
>
> https://github.com/mongodb/mongo-java-driver/commit/222d660e33015bce54b08845000c2ea77b944b32#diff-27c3bd4e56af669071c576ccec394864R227
>
> Babak
>
>
> Raul
Hello Babak,
Thanks for pointing this out!
Just some background... The ReadPreference class in the MongoDB Java API
has changed substantially between the driver versions:
* The initial contribution of camel-mongodb was done against driver version
2.7.3 [1].
* Currently we are on driver version 2
+1
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Tue, Mar 18, 2014 at 6:19 AM, Willem Jiang wrote:
> This is a v
+1. Will allow to use the Netty async provider packaged by AHC.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raul
The ASF Confluence is facing issues atm:
http://monitoring.apache.org/status/
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @
Hi,
I just performed a few component upgrades in preparation for the 2.13.0
release: async-http-client, Restlet, Shiro, Saxon, MongoDB Java driver.
All of them backported to 2.12.x too except for AHC, as it would have
implied a minor version upgrade (1.7.21 => 1.8.3), which I recall was
forbidden
+1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Sun, Feb 16, 2014 at 4:16 AM, Hadrian Zbarcea wrote:
> This i
+1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Sun, Feb 16, 2014 at 4:16 AM, Hadrian Zbarcea wrote:
> This i
+1.
On Fri, Nov 29, 2013 at 2:08 AM, Hadrian Zbarcea wrote:
> The camel:dot goal provided by the camel-maven-plugin has not been
> maintained in 5+ years, produces poor quality output and, most importantly,
> doesn't seem to be used. I propose to remove it.
>
> Hadrian
>
>
>
ut.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Nov 21, 2013 at 7:25 PM, Claus Ibsen wrote:
> Why is it you need that ClassLoader in the first place?
>
>
> On Wed, Nov 20, 2013 at 1:31 AM, Raul Kripalani wrote:
> >
ContextAware and have CamelContext injected.
> Though this only happens for services and whatnot Camel setup for you.
>
> Not sure if it the injection would happen for these classes you mention
> though.
>
>
> On Wed, Nov 20, 2013 at 1:31 AM, Raul Kripalani wrote:
> > He
Hi Johan
Any other ideas that could help solve the issue?
Thoughts welcome.
Thanks,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | t
nese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Wednesday, November 20, 2013 at 8:31 AM, Raul Kripalani wrote:
>
> > Hey guys,
> >
> > To solve CAMEL-6694, I'm having to enhance the constructors of the
> > CamelLogger and CamelLogProce
Hey guys,
To solve CAMEL-6694, I'm having to enhance the constructors of the
CamelLogger and CamelLogProcessor to pass in either:
- the ClassLoader of the Camel context (obtained with
CamelContext#getApplicationClassLoader) - or -
- the Camel context itself, letting the constructors call
If you're using Camel >= 2.10.3 or 2.11, enable the writeResultAsHeader
endpoint option.
In the future, please use the users@ forum for such queries. And please
remember to always indicate what version of Camel you're running on.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | En
Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Tue, Oct 8, 2013 at 12:36 AM, Raul Kripalani wrote:
> Hello fellow Apache folks,
&
Hello fellow Apache folks,
I'm writing on behalf of the Apache Camel project. We're eager to upgrade
to Apache HttpClient 4.3 for use by our camel-http4 component. In fact, we
already started the process [1] [2], but unfortunately we're faced with no
other option than to revert it due to HTTPCLIEN
Thanks, Christian.
I'm looking into it!
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Mon, Oct 7, 2013
I'm overloaded these days with client work. If someone else wants to take a
stab, you're welcome.
Otherwise, I'm hopeful I'll be able to review next week.
Regards,
Raúl.
2013/9/26 Jan Matèrne (jhm)
> Another "ping" ;)
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: Jan Matèrne (jhm) [m
Hi Jan,
I'll look into it today. Thanks for your contribution!
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raul
Hi Willem,
I think it could be clearer to use JUnit Assumptions [1] to disable a test
at runtime. The test would then show up as ignored rather than passed
(which would be misleading in this case).
[1] http://junit.sourceforge.net/javadoc/org/junit/Assume.html
Regards,
*Raúl Kripalani*
Apache C
Hi,
The ticket is resolved and the fix was included in several version lines.
Check out the JIRA ticket itself:
https://issues.apache.org/jira/browse/CAMEL-6123.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about
)
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Wed, Jul 31, 2013 at 11:01 PM, Raul Kripalani wro
Hi guys,
I'm reviewing Camel's XML-related components for hotspots to improve
performance.
Looking at the XmlConverter class, I've spotted a possible thread safety
issue with the documentBuilderFactory and transformerFactory instance
fields. They are lazily initialized once and re-used forever (p
+1
Raúl.
On Sun, Jul 14, 2013 at 11:05 AM, Jon Anstey wrote:
> +1
> On 2013-07-10 1:04 AM, "Hadrian Zbarcea" wrote:
>
> > This is a vote to release Apache Camel 2.11.1, a patch release coming
> with
> > about 110 issues fixed.
> >
> > Release notes:
> > https://issues.apache.org/**jira/secure/
competing frameworks talks about channels, deployment models
> controlling
> what to do or how to construct xml descriptors
>
>
>
> On Jul 11, 2013, at 5:59 PM, Raul Kripalani wrote:
>
> > Hi guys,
> >
> > For a few months I've been wanting to buil
Hi guys,
For a few months I've been wanting to build a set of utility classes with
the goal of providing a "toolbox" for commonly used AggregationStrategies,
OnPrepare processors, debug processors, etc.
Basically to make life easier for everyone. I feel there's too much
repeating that users can a
Hey Claus,
It's on my plate for this weekend.
Regards,
Raúl.
On Tue, May 28, 2013 at 12:18 PM, Claus Ibsen wrote:
> Possible 2 + 3 implemented.
>
>
> Raul did you by any chance had a chance to take a look also?
>
> What remains is gnodets suggest which has been listed as task 18.
> And then th
er this afternoon. Just
> running one extra fully sanity unit tests of the entire code base, to
> ensure no regressions or other gremlins introduced. Including all the
> OSGi tests which you need to run specially.
>
>
>
>
> On Sat, May 18, 2013 at 5:39 PM, Raul Kripalani wrote:
Hi Claus,
It's great that you're finding time for this. The need to lighten
stacktraces was already brought up within the Camel 3.0 context [1]. In
fact, there's also an entry in the roadmap page [2] which proposes moving
away from the recursive model into an iterative routing engine.
It's clear
+1.
*Raúl Kripalani*
Enterprise Architect, Open Source Integration specialist, Program
Manager | Apache
Camel Committer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Wed, Apr 17, 2013 at 9:11 PM, Christian Müller <
christian.
Vahdat" :
>
> >
> >
> > Am 14.04.13 13:09 schrieb "Raul Kripalani" unter :
> >
> > >Hi Claus
> > >
> > >+1 to redo the release.
> > >
> > >These stats are really useful for profiling.
> > >
> >
Hi Claus
+1 to redo the release.
These stats are really useful for profiling.
I'd rather turn the counters into plain longs and make it clear to users
(in the log statements and documentation) that the figures are merely
indicative and not fully accurate.
Regards,
Raúl.
On 14 Apr 2013 09:42, "
can remove the IdempotentOnCompletion
> from the exchange in our custom EventNotifier after we have executed it
> synchronous. Right?
>
> Best,
> Christian
>
>
> On Thu, Apr 4, 2013 at 5:37 PM, Raul Kripalani wrote:
>
> > BTW - In this Exchange Notifier, I suppos
t, Program
Manager | Apache
Camel Committer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Apr 4, 2013 at 4:28 PM, Raul Kripalani wrote:
> Hi Christian,
>
> I solved this once by using an ExchangeNotifier that proce
Hi Christian,
I solved this once by using an ExchangeNotifier that processes the Exchange
Completed events.
The callback is executed synchronously.
Mind you, there was a similar thread a few weeks ago, where more options
were presented. But I'm still doubtful about some of them being synchronous
1 - 100 of 186 matches
Mail list logo
