I believe I've encountered the bug. What I see is on reception, all
the entities proxies are made immutable.
They stay frozen, and finally, when flushing the driver, there is yet
another loop to freeze all the AutoBeans. Nowhere in between were the
beans made mutable. This is necessary because we sometimes have
custom setters we must call. In this case, we have the following:
@Override
public void saveTriggered() {
getValue().setActive(!view.isPracticeDeactivated());
save();
}
We need to invert the value of the check box, so we can't use the
checkbox directly as an editor. If I am creating a practice here
where the EntityProxy comes in from RequestContext.create() instead of
the server, everything is fine, the value is set to the proxy via this
call and save() proceeds to use the driver to flush changes. If the
entity proxy originated on the server however, calling set active
throws IllegalStateException("The AutoBean has been frozen");
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
