Claire,
Could you please share with us what you would like to do (project -->
routes --> process to be applied) otherwise that will not be possible ? As
your email contains two questions not related how would you
like
that we help you ?
Remarks : Exchange class of Camel is part of camel-core jar
Hi,
I used org.apache.camel.Exchange to modify my body but I got following
error:
Initialization of bean failed; nested exception is
java.lang.NoClassDefFoundError: org/apache/camel/Exchange
is there something I still need to define or add jar before I used Exchange?
Thanks,
Claire
--
View t
Done. Next is camel-2.11.3 this week.
Hadrian
On 11/22/2013 10:44 PM, Hadrian Zbarcea wrote:
The release is done, but for some reason the apache repo doesn't let me
close the staging repo:
The server did not close the staging repository.
Nexus returned an error: ERROR 502: Proxy Error
I'll tr
The vote passes with:
[5] +1 (ningjiang, davsclaus, hadrian, cschneider, cmueller)
[2] +1 - non-binding (ay, scranton)
[0] -1
I will proceed with publishing the artifacts today and make public
announcement of the release tomorrow, after the mirrors sync up.
Many thanks to all contributors,
Had
+1
Hadrian
On 11/22/2013 10:52 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.12.2, a patch release coming
with about 143 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325018
Staging repo:
https://reposito
Hi Christian,
thanks for your feedback.
In the affected environment that I have is based on gemini-web and
tomcat, where only the servlet 3.0 version is exported. So,
camel-servlet doesn't get activated out of the box. Simply changing
the import range will make it wired and also functional. So, I'l
We can do this but I think it is not necessary.
Implementations like pax web support the old package versions too to be
compatible with old builds.
Christian
Am 26.11.2013 12:39, schrieb Aki Yoshida:
Hi,
I noticed this a while ago but forgot to bring it up or ask.
Currently, the import versi
+1
Christian
Am 23.11.2013 04:52, schrieb Hadrian Zbarcea:
This is a vote to release Apache Camel 2.12.2, a patch release coming
with about 143 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325018
Staging repo:
https://rep
Hi,
I noticed this a while ago but forgot to bring it up or ask.
Currently, the import version range of javax.servlet is not explicitly
given in camel-servlet's pom and as a result, camel-servlet is
importing javax.servlet with range "[2.6,3)".
Could we set the range explicitly to something like
GitHub user ge0ffrey opened a pull request:
https://github.com/apache/camel/pull/62
camel-optaplanner: production code + unit test
The camel-optaplanner component takes the body of a request, for example an
unsolved TSP problem, then solves it and returns it as the body of the respo
+1
Tested with some of my private projects.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Sat, Nov 2
+1 (non-binding)
ran the install test and some cxf osgi tests. All OK.
the only thing I noticed was one unit test in camel-dns that seems to
fail in sometimes semi-permanently.
if your run from your console
dig +short txt monkey.wp.dg.cx
and that is not returning the string
"A Macaque, ... http
12 matches
Mail list logo
