Hi,
As per my understanding, shutdown strategy is set per camelcontext.
Is there a way / other ways where we can apply shutdown strategy or custom
shutdown implementation per route(s) in a camel context?
In my use case, i have number of events stored in database already. In order
to avoid reproce
This route is working correctly.
There is a datatype issue for date fields for sql component. but i am sure
there is not an easy way to fix it.
because sql component may be running for different vendor.
for keeping simple i converted date datatype to string representation by
using sql features.
fo
Hi,
I have a route as below;
from("seda:A?concurrentConsumers=2")
.enrich("sql:select X from test_table where id =
:#${body.getId}?outputClass="
+ MyX.class.getName()", new
AggregationStrategy() {
@Override
public Exchange agg
Hello,
I want to ask you question about a design choice. (maybe there is an
existing EIP / composite EIPS together out of box, which i am not already
familiar )
Think of you have X number of rows in a table. (which will continuosly get
new rows)
And you want to consume every row in that table an
please see the methods
createClientFactory[1], in CxfEndpoint or CxfSpringEndpoint classes.
I think based on your client stubs, Camel creates instances of client stub
objects, so i suppose this depends and client stub classes and your
configuration.
[1]
https://github.com/apache/camel/blob/mas
Hi,
Split eip supports tokenizing by a delimiter and grouping as below;
from("file:inbox")
.split().tokenize("\n", 1000).streaming()
.to("activemq:queue:order");
Is there a specific reason why we don't have such like.
from("file:inbox")
.split().tokenizeByByteSize(1024, 1000).streaming
btw, i tried both leveldb and hawtdb as aggregationrepository.
or
--
View this message in context:
http://camel.465427.n5.nabble.com/Aggregator-LevelDB-or-HawtDB-for-persistency-incorrect-behavior-tp5765524p578
Hi,
I am usign all camel core and components as of 2.17.3.
This issue seems to be still up.
Under examples/camel-example-aggregator i can test it is working.
as of route below; aggregation is not completed and not output file is
getting generated. (btw, if i do aggregate without persistence, it
any idea?
--
View this message in context:
http://camel.465427.n5.nabble.com/CacheProducer-requiring-the-same-config-params-in-java-dsl-tp5786061p5786180.html
Sent from the Camel - Users mailing list archive at Nabble.com.
One of my friend is having such an issue as stated on stackoverflow.
Does anyone have an idea?
http://stackoverflow.com/questions/37488705/apache-camel-cache-configuration-is-not-working/38728611#38728611
Thx
--
View this message in context:
http://camel.465427.n5.nabble.com/CacheProducer-re
i would expect the latter one as far i understand.
test routes of these 3 steps would make it more clear
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-FTP-design-issue-tp5784192p5784193.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ConcurrentModificationException happens to be due the fact that you are
trying to modify the collection whereas you are traversing it.
It's hard to help you unless we know some details of design of your route.
If you can provide details, we can give it a shot..
--
View this message in context:
thanks for the guidance.
--
View this message in context:
http://camel.465427.n5.nabble.com/DefaultSqlPrepareStatementStrategy-lookupParameter-when-onConsume-used-in-SQL-component-tp5780437p5780671.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hmm.. I think i misunderstood the route conceptually.
What i thought was that below is a single route;
from("sql:select rowid vrowid from myTable where nstatus = 0?outputClass=" +
MyBean.class.getName()
+ "&onConsume=update myTable set nstatus = 1 where rowid =
:#${body.getVrowid
no, this does not help :(
when i debug, interestingly i can see onConsume gets exhange's body as the
output of bean bound on from("direct:generateLine"...) route which is
LineGenerator..
from("sql:select rowid vrowid from myTable where nstatus = 0?outputClass=" +
MyBean.class.getName()
Here it is;
import java.io.Serializable;
public class MyBean implements Serializable {
/**
*
*/
private static final long serialVersionUID = 1L;
private String vrow_id;
public String getVrow_id() {
return vrow_id
I think the code snippet i sent earlier had outputClass option missing.
(I was playing it around).
So what i meant to describe was as the following...
from("sql:select rowid vrow_id from myTable where nstatus =
0?*outputClass=" + MyBean.class.getName()
+ "*&onCons
Hi,
This is the route code.
from("sql:select rowid vrow_id from myTable where nstatus = 0" +
MyBean.class.getName()
+ "&onConsume=update myTable set nstatus = 1
where VROW_ID =
:#${body.vrow_id}")
.r
Did anybody have a chance to look at it?
Regards
Önder
--
View this message in context:
http://camel.465427.n5.nabble.com/DefaultSqlPrepareStatementStrategy-lookupParameter-when-onConsume-used-in-SQL-component-tp5780437p5780585.html
Sent from the Camel - Users mailing list archive at Nabble.co
Hi,
I have a simple route as the following;
from("sql:select rowid vrow_id from myTable where nstatus = 0" +
MyBean.class.getName()
+ "&onConsume=update myTable set nstatus = 1
where VROW_ID =
:#${body.vrow_id}")
.ro
20 matches
Mail list logo
