I ran the examples tests and camelinaction unit tests with this kit.
All the tests were passed. I also ran some OSGi Karaf test, they were
looking good.
Here is my +1.
Even my MBP was broken when running the release build and it took my more
time to run the release processes with my old MBP :) .
After 5 month of development, we have a new minor release candidate
apache-camel-2.12.0 ready.
It comes with 350 issues resolved: new features, improvements and bug
fixes[1]
. You can find the release notes here [2].
The issues we found in Camel 2.12.0 (RC1), such as including camel-core
test jar
The Apache Jenkins build system has built Camel.trunk.notest (build #1980)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1980/
to view the results.
The Apache Jenkins build system has built Camel.2.12.x.notest (build #9)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/9/ to
view the results.
Hi
Good idea as from Camel 2.12 onwards we have a StreamCachingStrategy
which allows us to safely use CachedOutputStream in components without
forcing spooling to disk on end-users, without them knowing that.
Fell free to log a JIRA ticket.
On Wed, Sep 4, 2013 at 11:14 AM, Franz Paul Forsthofer
Hello,
the MarschallProcessor currently returns a byte array. This does mean that
large messages are kept in memory which can lead to performance problems. I
suggest to use StreamCache instead by using CachedOutputStream instead of
ByteArrayOutputStream.
To be more concret, instead of
publi
Hi Christian,
Just created a account on the Confluence WIKI and the user name is
'pontus.ullgren'.
Best regards
Pontus Ullgren
On 2013-09-02 19:34, Christian Müller wrote:
Hi Pontus,
you ICLA was received and filed by the Apache secretary and I wanted
go ahead and grant the WIKI karma for A
