Guys,
Is this OneToMany a true OneToMany? I guess it only applies when the entire
CSV file has some common elements? I have a file that has entries like
below:
1,abc,def,joe
1,abc,xyz,san
2,abc,mno,ram
3,abc,fgh,sam
When I tried with the above file which used the OneToMany annotation between
the
Hi,
Thanks for reporting this.
I just filled a JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-6544
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.
I'm testing my upgrade to 2.11 and noticed a bug in how beanMethod
invocations are parsed.
I'm using Spring to define my routes.
The following invocation expression: exec(*, '', 'arg3') gets parsed as
arg1: *
arg2: ""
arg3: ",arg3" (notice the comma).
I tracked down the bug to the class org.apa
Yep, I was thinking about this approach as well.
Using Seda is the transnational integrity preserved?
Let say the delivery of one message using seda fails, does camel recognize
it and redeliver it?
-
Alireza Salemi
--
View this message in context:
http://camel.465427.n5.nabble.com/Inco
Guys,
I face a strange error when trying to use the camel-bindy component!
The separator has not been defined in the annotation @CsvRecord or not
instantiated during initModel.
I have specified this in the annotation. I checked the old posts by doing a
simple search and I came to know that this
This is what I do to initialize the bindy component!
DataFormat bindy = new BindyCsvDataFormat("com.test.mypackage.csvdata");
The package contains the classes that are annotated with the @CsvRecord
annotation. The package also contains some other classes that do not have
this annotation. But I gu
I tried using version 2.9.x, but that seems not to be feasible as all the
other modules use 2.8.0 and I get dependency path initialization errors when
it is trying to resolve the camel core libraries. Is there another way to
get around this issue?
Regards,
Joe
--
View this message in context:
I can now see that it is fixed in versions 2.8.2 and above. But this brings
me another question. Even though I use Camel 2.8.0, can I use version 2.9.0
for the bindy component?
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735582.html
Sent fr
After a bit of fiddling with it, I had to give up on the bindy component as
it does not fit to what I have. My domain model consist of a parent class
and a sub class where some of the fields are annotated in the parent class.
But this leads to an error when used with the bindy component. So this do
i'm new in camel. i want to design a camel application which sync two
servers.
server1:
this server send a message to camel application. this message has a HTTP
link which we should download and this downloaded message has another
multiple HTTP link which we should download by HTTP GET request and
Hi,
I have a route with an onException that references a spring bean redelivery
policy. It appears that the reference is not working as I have a
maximumRetries set but no retries are attempted. If I use the onException
with a child element it works
fine.
Does anyone know how to make this work?
Thanks for the great responses. They are very helpful.
After discovering more about the problem domain, it appears that our clients
do not always adhere to the file format. For example, in a standard file,
positions 10-20 may represent the account number. Client 1 sends files that
adhere to thi
I have a Bindy bean written as below:
public class ObjectMaster {
private String field1;
@OneToMany
private List < Object1 > field2;
@OneToMany
private List < Object2 > field3;
}
I have two CSV files in which unmarshalling one of them would produce a one
to many relationshi
I'm considering the Bindy component to marshall and unmarshall stuff. I can
see that there is a OneToMany annotation that I can use. Will the OneToMany
only map to a List or can I use a Set as well?
--
View this message in context:
http://camel.465427.n5.nabble.com/CSV-files-processing-tp573547
Hi
I am using the camel-cxf example and created a project in eclipse.
In src/main/java
org.apache.camel.example.Provider package, I created my own Client which
talks to end application.
I used this client in my CamelCxfExample.java Class and modified the tester
bean as well.
Now I modified the Ca
Hi again,
Is this problem existing, due to camels own XsltUriResolver?
It seems that camels XsltUriResolver only is capable to handle files
either from the classpath or the file system.
With the xlst function, document(''), the xslt processer should be able to
handle that the result "is the sour
Hi all!
I've been using Camel in the last 2 weeks, so I'm relatively new into its
usage.
After reading the doc and several howtos, I'm a bit struck in a point, and
I'd like to ask you if I'm doing something wrong.
My Camel route consumes an external SOAP WS in POJO mode and, afterwards,
sends i
You have different options:
1) use Bindy the Willem's way (bear in mind that if you use two data format
classes you have to place them in different top-level packages)
2) use Bean-IO and do something like:
final Predicate predicateOrder = body().startsWith("01");
final Predicate predicateCus
18 matches
Mail list logo