Let me start with I have a solution, but I don't really think it is elegant. So, I am looking for a cleaner way to do this.
I have an EntityProxy displayed in a view panel.
The view panel is a RequestFactoryEditorDriver only using display mode.
The user clicks on a data element and opens a popup editor to edit a data element of
the EntityProxy with a few more bits of data than is displayed in
the view panel. When
the user saves
the element I need
the view panel to update
the display.
I ran into a problem because
the RequestFactoryEditorDriver of
the popup editor flow doesn't let you get to
the edited data.
The driver uses
the passed in context and sends it to
the server.
The context returned out of flush only allows a Receiver even if you cast it to
the type of context you stored in
the editor driver in
the edit() call. It doesn't appear to send and EntityProxyChanged event either, so I couldn't listen for that and update
the display view.
The solution I found was to change my domain object persist to return
the newly saved entity. Then create
the popup editor like this
editor.getSaveButtonClickHandler().addClickHandler(createSaveHandler(driver, editor));
// initialize
the Driver and edit
the given text.
driver.initialize(rf, editor);
PlayerProfileCtx ctx = rf.playerProfile();
ctx.persist().using(playerProfile).with(driver.getPaths())
.to(new Receiver<PlayerProfileProxy>(){
@Override
public void onSuccess(PlayerProfileProxy profile) {
editor.hide();
playerProfile = profile;
viewDriver.display(playerProfile);
}
});
driver.edit(playerProfile, ctx);
editor.centerAndShow();
Then in
the save handler I just
fire the context I get from
the flush. While this approach works, it doesn't seem right. It would seem I should subscribe to
the entitychanged event in
the display view and update
the entity and
the view from there. Also this approach saves
the complete entity, not just
the changed bits, which will increase bandwidth usage.
What I would think should happen, is when you flush
the entity it should 'optimistically' update
the rf managed version of
the entity and
fire the entity proxy changed event. Only reverting
the entity if something went wrong in
the save.
The actual save should only send
the changed bits. In this way there isn't a need to refetch
the whole entity and send that complete data over
the wire twice.
Is there a better solution?
