You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Jothi <co...@gmail.com> on 2013/07/12 21:15:05 UTC
Error in camel-bindy
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 was fixed in Camel 2.7. I use the
version 2.8.0.fuse-01-06. Is there a bug still unfixed or un ported to the
version that I'm using?
Regards,
Joe
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Claus Ibsen <cl...@gmail.com>.
No
On Mon, Jul 15, 2013 at 4:03 PM, Jothi <co...@gmail.com> wrote:
> Is it possible with Camel 2.8.0 to provide the class name instead of the
> package name to the unmarshall dsl?
>
> Can I instead of
> .unmarshal(new BindyCsvDataFormat("de.test.model")
>
> do
> .unmarshal(new BindyCsvDataFormat("de.test.model.MyModel")
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735671.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
As I understand from Claus's message is that it is not possible to specify
the class name to the BindyCsvDataFormat as this feature seems not to be
available with the camel version that I'm using!
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735828.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by "rameshkumar.m" <ra...@gmail.com>.
Hi Jothi,You can do like this.*.unmarshal(new
BindyCsvDataFormat(de.test.model.MyModel.class);*
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735825.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
Is it possible with Camel 2.8.0 to provide the class name instead of the
package name to the unmarshall dsl?
Can I instead of
.unmarshal(new BindyCsvDataFormat("de.test.model")
do
.unmarshal(new BindyCsvDataFormat("de.test.model.MyModel")
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735671.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Christian Müller <ch...@gmail.com>.
What issue do you hit?
You should define the dependency to 2.9.x in your pom and exclude
duplicated dependencies to 2.8.x.
Executing mvn dependency:tree is helpful.
Best,
Christian
-----------------
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Jul 12, 2013 at 10:30 PM, Jothi <co...@gmail.com> wrote:
> 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 does
> not fit my needs. Had to give up on the bindy component.
>
> Regards,
> Joe
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735584.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
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 does
not fit my needs. Had to give up on the bindy component.
Regards,
Joe
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735584.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
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: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735583.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
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 from the Camel - Users mailing list archive at Nabble.com.
Re: Error in camel-bindy
Posted by Jothi <co...@gmail.com>.
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 guess this should not be a problem.
Regards,
Joe
--
View this message in context: http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735581.html
Sent from the Camel - Users mailing list archive at Nabble.com.