RequestFactory complexity (Frozen Beans et. all)

I really want to like RequestFactory, really I do, but I'm astounded
by the complexity. I finally got my head around the Locator, the
proxies, etc and now I'm getting Frozen beans and "edited by another
RequestContext" errors.

I took a look at: http://fascynacja.wordpress.com/tag/autobean-has-been-frozen/
and this helped alot, but I'm astounded that my code has to trap for
all this stuff.

1. Does anyone know if the GWT is going to change so that this state
doesn't have to be managed?
2. Anyone have any helper classes that can trap for this stuff?
3. Any best practices?

All I want to do is:
1. Edit a previously loaded entity
2. Create a new entity and save it

I must be making this harder than it actually is or else very few
folks use this successfully.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.