[#CAMEL-430] consumeDelete=false option of etl sample doesn't seem to work - Apache ActiveMQ, Apache ServiceMix, Apache Camel

Apache Camel

consumeDelete=false option of etl sample doesn't seem to work

Created: 02/Apr/08 12:20 PM Updated: 12/May/08 05:45 AM

Return to search

Component/s:

camel-jpa, examples

Affects Version/s:

1.2.0, 1.3.0

Fix Version/s:

1.3.0

Time Tracking:

Not Specified

Description

« Hide

In org/apache/camel/example/etl/EtlRoutes.java, the following line:

from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false?consumer.delay=3000&consumeLockEntity=false")
        .setHeader(FileComponent.HEADER_FILE_NAME, el("${in.body.userName}.xml"))
        .to("file:target/customers?append=false");

seems to successfully dump the database entries to files in the target/customers directory. Unless I'm misunderstanding the sample, the consumeDelete=false is meant to ensure that the dump of the database does not delete the entries from the database. However, when running the etl sample querying the customer table in the database, the list is empty. I suspect the consumeDelete=false isn't working.

All

Comments

Work Log

Change History

Subversion Commits

FishEye

Crucible

Sort Order:

Claus Ibsen made changes - 02/Apr/08 09:50 PM

Field	Original Value	New Value
Component/s		camel-jpa [ 11645 ]
Description	In org/apache/camel/example/etl/EtlRoutes.java, the following line: from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false?consumer.delay=3000&consumeLockEntity=false") .setHeader(FileComponent.HEADER_FILE_NAME, el("${in.body.userName}.xml")) .to("file:target/customers?append=false"); seems to successfully dump the database entries to files in the target/customers directory. Unless I'm misunderstanding the sample, the consumeDelete=false is meant to ensure that the dump of the database does not delete the entries from the database. However, when running the etl sample querying the customer table in the database, the list is empty. I suspect the consumeDelete=false isn't working.	In org/apache/camel/example/etl/EtlRoutes.java, the following line: from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false?consumer.delay=3000&consumeLockEntity=false") .setHeader(FileComponent.HEADER_FILE_NAME, el("${in.body.userName}.xml")) .to("file:target/customers?append=false"); seems to successfully dump the database entries to files in the target/customers directory. Unless I'm misunderstanding the sample, the consumeDelete=false is meant to ensure that the dump of the database does not delete the entries from the database. However, when running the etl sample querying the customer table in the database, the list is empty. I suspect the consumeDelete=false isn't working.
Affects Version/s		1.2.0 [ 11822 ]
Affects Version/s		1.3.0 [ 11840 ]
Fix Version/s		1.4.0 [ 11849 ]

[ Permlink | « Hide ]

Claus Ibsen added a comment - 02/Apr/08 09:51 PM

A few other options hasnt been documented

flushOnSend (default = true)
maximumResults (default = -1)

Claus Ibsen made changes - 02/Apr/08 09:51 PM

Description

In org/apache/camel/example/etl/EtlRoutes.java, the following line:

    from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false?consumer.delay=3000&consumeLockEntity=false")
        .setHeader(FileComponent.HEADER_FILE_NAME, el("${in.body.userName}.xml"))
        .to("file:target/customers?append=false");

seems to successfully dump the database entries to files in the target/customers directory. Unless I'm misunderstanding the sample, the consumeDelete=false is meant to ensure that the dump of the database does not delete the entries from the database. However, when running the etl sample querying the customer table in the database, the list is empty. I suspect the consumeDelete=false isn't working.

In org/apache/camel/example/etl/EtlRoutes.java, the following line:

{code}
    from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false?consumer.delay=3000&consumeLockEntity=false")
        .setHeader(FileComponent.HEADER_FILE_NAME, el("${in.body.userName}.xml"))
        .to("file:target/customers?append=false");
{code}

seems to successfully dump the database entries to files in the target/customers directory. Unless I'm misunderstanding the sample, the consumeDelete=false is meant to ensure that the dump of the database does not delete the entries from the database. However, when running the etl sample querying the customer table in the database, the list is empty. I suspect the consumeDelete=false isn't working.

[ Permlink | « Hide ]

Claus Ibsen added a comment - 02/Apr/08 10:08 PM

It was just a mistyped URI in the sample.

The JPA component works fine.
I will spin off a new task for the missing options in the wiki