Thanks, Thomas. I came back here just to report that. I had designed
my services to take Entities (and EntityProxies on the GWT side) as
arguments to "filter" what the Selector will return as its list of
choices out of habit of design. I should have considered passing the
ID from the start given that these arguments are serialized and passed
over the wire. What threw me off was that the argument used for the
Selector was a property of my root Editor's main EntityProxy, not the
root EntityProxy itself, so I was initially at a loss when the error
said I was trying to edit an EntityProxy already being edited. Also,
I wasn't editing the arguments, just using them as parameters - but
GWT RF of course doesn't know that.
Passing the ID as you suggested cleared this up. Thanks for your feed
back. Your posterous posts have been a lifesaver, btw.
-B