Metawidget

I think that the JavaBeanPropertyStyle in order to be more consistent, could have a behavior closer to the actual Java Beans conventions. So, it should not consider public fields, and it's implementation could rely on the convention, after all, this is what JavaBean is, right?

Perhaps, the main problem here is how to handle the private fields annotations, in order to support the existing annotations based back-end architectures properly, not necessarily how it access the fields. I believe that is reasonable to use the getters/setters as default for ACCESSING, which also solves the binding compatibility problem you mentioned, and I don't see why it would need to access the private fields values directly. Of course, there might be a need for it, but this is another problem, and in this case the MW would allow to plug this behavior.

It would be nice to support by default the main back-end archs, or at least most of them, without having to write or configure. For instance, if I use JPA/JDO with field access for my project, it won't work as it is today without having to write a new PropertyStyle. This is too basic and would discourage one to use MW! So, I think it would be fundamental to have a PropertyStyle that supports this in the distribution, and preferably, as default.

I did a small change into JavaBeanPropertyStyle to attend my needs, and created a new custom version. I'll do some testing and let you know.

Thanks and regards,
Renato