There're are two extensions of JCR Node apaters atm in the content editor module: one for the JcrNodeAdapter itself, the other - for its "new" variation. The wrappers exist for one purpose: auto-generate the queried Vaadin item property if the corresponding property exists in JCR (or just create it for the new node adapter).

This behaviour seems to be conflicting with other node adapter related features and at least for the case of JcrNodeAdapter - duplicate the logic that is already there!

We should remove those wrappers and probably swallow the bullet and explicitly add the properties to the items when they're missing (luckily we can add such logic to the block model implementation).