|
If you were logged in you would be able to see more operations.
|
|
|
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.
|
|
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. |
Show » |
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
]
|
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.
|
made changes - 02/Apr/08 10:08 PM
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
made changes - 02/Apr/08 10:09 PM
|
Assignee
|
|
Claus Ibsen
[ davsclaus
]
|
made changes - 03/Apr/08 04:10 PM
|
Fix Version/s
|
1.4.0
[ 11849
]
|
|
|
Fix Version/s
|
|
1.3.0
[ 11840
]
|
made changes - 12/May/08 05:45 AM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Bug
Closed
Major
consumeDelete=false option of etl sample doesn't seem to work
