Today I checked out the new JPAContainer 3.1.0 along with updated Vaadin 7.1.5 (I had been using 7.1.0).
It seems to me that JPAContainer’s FieldFactory only works with a deprecated API.
With JPAContainer, one used to be able to autobuild a form in which not only did normal properties get the correct component (like a TextField for Strings), but also properties that were references to other JPA Entities (like a @OneToOne property) also got themselves a nice proper component (a Select/ComboBox listing the instances of the other JPAEntity, pulled from the database).
It seems that the new JPAContainer 3.1, which is finally compatible with Vaadin 7.1.X, can only provide JPA-aware Fields if one uses the old, deprecated “Form” construct. The new FieldGroup doesnt seem to be supported.
¿any idea why that is, and wether there are plans to bring back JPA-aware field support to the latest release of Vaadin?