There seems to be a bug in the field to POJO mapping. Typically, with Java Beans, if you have a value named "firstName" it will find the setter "setFirstName". Consider JSON parsing libraries like JSON or GSON.
Unfortunately, with JOOQ, it will only look for "setfirstName", "setfirstname", or "setFirstname". It might be a limitation instead of a bug but it feels like a bug. Personally, I would consider making the first match be "set" + name.substring(0,1).toUpper() + name.substring(0, name.length). Then all will be well (and as expected). I'm actually surprised this hasn't been a bigger issue with how mature the JOOQ codebase is. Was there a reason for not adopting the same bean mapping rules other domains (like JSON) adopt? Thanks! -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
