View model proxying

I checked out the brewery buddy sample and in the toString of Category i noticed the comment

// Must use getters instead of direct member access, // to make it work with proxy objects generated by the view model

Would this be a problem if the entity would be tossed through a JAX-RS client that would serialize with field access?

Yes, that might be a problem. The original plan allowed to work around that was that we’d provide a method for writing non-proxied values into a non-proxy instance. We have, however, not yet prioritized actually implementing that functionality. See for more details.