Camel.2.18.x.notest - Build # 83 - Fixed

2017-03-02 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Camel.2.18.x.notest (build #83)

Status: Fixed

Check console output at https://builds.apache.org/job/Camel.2.18.x.notest/83/ 
to view the results.

Camel.2.17.x.notest - Build # 188 - Fixed

2017-03-02 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Camel.2.17.x.notest (build #188)

Status: Fixed

Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/188/ 
to view the results.

Camel.trunk.notest.java9 - Build # 19 - Still Failing

2017-03-02 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Camel.trunk.notest.java9 (build #19)

Status: Still Failing

Check console output at 
https://builds.apache.org/job/Camel.trunk.notest.java9/19/ to view the results.

[GitHub] camel pull request #1503: Camel 10141 This builds Camel on Java 9

2017-03-02 Thread johnpoth 
Github user johnpoth closed the pull request at:

https://github.com/apache/camel/pull/1503


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1503: Camel 10141 This builds Camel on Java 9

2017-03-02 Thread johnpoth 
GitHub user johnpoth opened a pull request:

https://github.com/apache/camel/pull/1503

Camel 10141 This builds Camel on Java 9

https://issues.apache.org/jira/browse/CAMEL-10141

This builds Camel on Java 9. Before building you must set
```
MAVEN_OPTS="--add-modules java.activation 
--add-exports=java.xml/com.sun.org.apache.xml.internal.resolver.tools=ALL-UNNAMED
 --add-exports=java.xml/com.sun.org.apache.xml.internal.resolver=ALL-UNNAMED 
--add-opens java.base/java.text=ALL-UNNAMED --add-opens 
java.desktop/java.awt.font=ALL-UNNAMED --add-opens 
java.base/java.util=ALL-UNNAMED  --add-opens java.base/java.lang=ALL-UNNAMED 
--add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens 
java.base/java.util.regex=ALL-UNNAMED --add-opens 
java.base/java.net=ALL-UNNAMED"
```

I've added some scripts under buildingtools for convenience.

Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/camel CAMEL-10141

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1503.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1503






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1502: CAMEL-10927: Added KafkaIdempotentRepository

2017-03-02 Thread jkorab 
GitHub user jkorab opened a pull request:

https://github.com/apache/camel/pull/1502

CAMEL-10927: Added KafkaIdempotentRepository

Pull request contains Kafka topic-based IdempotentRepository. Also contains 
refactorings of existing camel-kafka test support classes that were required to 
simplify the embedded Kafka and Zookeeper implementations, and fixed 
state-leakage issue in unit tests.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jkorab/camel CAMEL-10927

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1502.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1502


commit ea4089e9eb7a55fef65d780a74c5c4191f0f22ab
Author: Jakub Korab 
Date:   2017-02-24T13:51:26Z

Kafka test resource refactoring

commit 00c479958943c158b9ba75f6006060380eaf53b4
Author: Jakub Korab 
Date:   2017-02-28T17:23:50Z

Refactored embedded test infrastructure

commit 43df88ef8eab22dd868f96a53e0586297be81846
Author: Jakub Korab 
Date:   2017-03-02T15:14:07Z

CAMEL-10927 Added complete KafkaIdempotentRepository with supporting tests.

commit 86ca918f71e25c57b925670d78abcf1de05a087e
Author: Jakub Korab 
Date:   2017-03-02T15:20:40Z

Removed unnecessary synchronized block.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1501: CAMEL-10908 Fixed adoc

2017-03-02 Thread igarashitm 
Github user igarashitm closed the pull request at:

https://github.com/apache/camel/pull/1501


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Sjms batch consumer

2017-03-02 Thread Claus Ibsen 
Hi

Please use the user forum / @user mailing list for these kind of questions

On Wed, Mar 1, 2017 at 11:59 PM, sutoa  wrote:
> Hi,
> I'm trying to use Camel SJMS to batch process messages from IBM MQ.
> As a first step, I am using activeMQ.
> My goal is to batch read a chunk of messages from JMS, do some processing
> and insert them to a database. From reading some old posts, I am doing the
> following.
> from("sjms:myq?transacted=true=1000").process(myProcessor)
>
> My processor gets exchanges at the single message level instead of 1000
> messages in one go. This is consistent with what i read. My question is that
> how does SJMS coordinate the transaction management between Q and db? i
> didn't add any Transaction Manager in the camel context. Will all my db
> inserts be bundled into one batch commit?
> When I worked on some other project in Spring Integration, I used to have to
> provide a transaction manager to the app context to be shared by the JMS
> message listener and the database datasource.
>
> Thanks,
> Tong
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Sjms-batch-consumer-tp5794644.html
> Sent from the Camel Development mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

[GitHub] camel pull request #1500: CAMEL-10914: Apply the same fix as CxfConsumer to ...

2017-03-02 Thread tadayosi 
Github user tadayosi closed the pull request at:

https://github.com/apache/camel/pull/1500


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---