Yeah there is some ReflectionHelper in camel-core it could reuse instead, then we could add logic for checking for setter first and use that, and if not fallback on direct fields.
On Wed, Jun 17, 2015 at 2:04 PM, Giorgio Vespucci <giorgio.vespu...@gmail.com> wrote: > Thank you for the hint Claus > Indeed I found the following sentences in the source code: > > // Get Field to be setted > Field field = annotatedFields.get(pos); > field.setAccessible(true); > > [...] > > field.set(modelField, value); > > Then it would mean today it definitively uses reflection. > > > On Wed, Jun 17, 2015 at 12:20 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > >> Hi >> >> Sorry but I would refer to looking at the source code. >> >> But yeah ideally it should use setter over direct fields if possible. >> But the source code will tell what it does today. >> >> On Wed, Jun 17, 2015 at 12:01 PM, Giorgio Vespucci >> <giorgio.vespu...@gmail.com> wrote: >> > Hi everybody :) >> > I'm wondering how Bindy is setting values from a CSV file to Java fields. >> > >> > It looks that it's not using setter methods the POJO exposes. >> > Is there a way to intercept Bindy setter actions, so that an additional >> > behavior could be executed? >> > >> > I'm using Camel 2.14.3. >> > >> > Best regards and thank you. >> >> >> >> -- >> Claus Ibsen >> ----------------- >> Red Hat, Inc. >> Email: cib...@redhat.com >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen >> hawtio: http://hawt.io/ >> fabric8 <http://hawt.io/fabric8>: http://fabric8.io/ >> -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
