On Wed, Dec 10, 2014 at 10:04 AM, Christian Schneider
wrote:
> I agree with Dan that a common module and one module for jetty8 and one for
> jetty9 is probably the best route to go. Like Willem mentioned we can even
> try to create a http common module if possible. I would start with a jetty
> bas
Hi Daniel,
I already cut a release candidate of Camel 2.14.1, the fix is a bit late.
Regards,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 11, 2014
Status report for the Apache Camel project - December 2014
Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--
* There are no issues that require the board attention.
* The project is healthy, active and stays
On 10/12/14 12:15, Willem Jiang wrote:
> Please don’t do any commit to Camel-2.14.x branch until you see the new
> camel-2.14.1 tag is created.
>
Is it too late to drop in my fix for CAMEL-8142?
https://github.com/apache/camel/pull/355
GitHub user dpocock opened a pull request:
https://github.com/apache/camel/pull/355
camel-sql: add outputHeader parameter (CAMEL-8142)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dpocock/camel dpocock-sql-outputheader
Altern
It sounds good to me, we can do the http common module work later.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 10, 2014 at 5:06:02 PM, Christian Schn
Please don’t do any commit to Camel-2.14.x branch until you see the new
camel-2.14.1 tag is created.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 9,
I replied to your "camel -xsd" thread at users@camel.
I think that clarifies your question.
regards, aki
2014-12-10 10:27 GMT+01:00 Aki Yoshida :
> The test cases are spread in several places depending on the test types.
>
> For the iterator-level tests, those XMLTokenExpressionIterator*Test.java
The test cases are spread in several places depending on the test types.
For the iterator-level tests, those XMLTokenExpressionIterator*Test.java in
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tree;f=camel-core/src/test/java/org/apache/camel/support/
For the xtokenizer-level tests, tho
I agree with Dan that a common module and one module for jetty8 and one
for jetty9 is probably the best route to go. Like Willem mentioned we
can even try to create a http common module if possible. I would start
with a jetty based common module first as it is probably the easier step.
I am no
I played a little bit with the new split().xtokenize() method (user list
"camel - xsd" thread).
And I have seen a bug - but I am not sure whether it's in the computer or in
front of ;)
Where are the unit tests for xml splitting with xtokenize()?
Jan
11 matches
Mail list logo
