0

The following snippet displays the list of Cats successfully, however when I flush the driver the values in the Cat objects are all null.

The name of the cat house can be edited as expected.

HasDataEditor<CatProxy> residentsEditor= HasDataEditor.of(cellTable)

CatHouse{
    String name;
    List<Cat> residents;
}
Cat{
    String name;
    String favoriteColor;
}

Here is how I am creating the request. (Adapted from the MobileWebApp sample project)

// Flush the changes into the editable CatHouse.
final CatHouseRequest context = (CatHouseRequest) clientFactory.getCatHouseEditView().getEditorDriver().flush();

/*
 * Create a persist request the first time we try to save this task. If
 * a request already exists, reuse it.
 */
if (taskPersistRequest == null) {
    taskPersistRequest = context.updateCatHouse(editTask).with(
            clientFactory.getCatHouseEditView().getEditorDriver().getPaths());
}

// Fire the request.
taskPersistRequest.fire(new Receiver<ActionProxy>() {
    @Override public void onConstraintViolation(final Set<ConstraintViolation<?>> violations) {
        ...
    }

    @Override public void onSuccess(final CatHouseProxy response) {
        ... 
    }
});

I've inspected the taskPersistRequest variable right before it was fired.

  • taskPersistRequest.propertyRefs = [catHouse]

  • taskPersistRequest.requestContext has the correct values for the CatHouse and the Cats.

  • taskPersistRequest.requestData.parameters only has one value for CatHouse with no data related to Cats. (This looks like the problem)

  • The editProxies variable in context has the correct values for the CatHouse and Cat.

Nick Siderakis
  • 1,961
  • 2
  • 21
  • 39

1 Answers1

1

I ran into a similar problem today. If you create the CatHouse before the Cat items are created, on the same RequestContext, persisting the CatHouse will fail, because the Cat items are not available yet.

To fix this: create the Cat beans first and create the CatHouse beans afterwards:

cat = request.create(Cat.class)
catHouse = request.create(CatHouse.class)

Implementing this when using the editor framework is not trivial, however, since it requires you to pass an instance of CatHouse in the editor driver before the editor will trigger the creation of the Cat instances.

A possible workaround is to copy the flushed auto bean on a new request context in a way that the Cats are created before the CatHouse is.

(In case you're not creating, but simply editing the cat house, think in terms of request.edit(catHouse) rather than request.create(CatHouse.class))

fabiangebert
  • 2,623
  • 2
  • 22
  • 25
  • Thanks for the answer. I'm trying to edit the CatHouse's Cats (They were added on the server side when CatHouse was first persisted). Does edit need to be called on each Cat that is updated? I was hoping calling edit on the catHouse would make its Cats editable. – Nick Siderakis Jun 04 '11 at 13:35
  • Yeah, you need to call .edit for each of the Cat objects and pass the return value of the .edit (a mutable proxy that is) to the Editor. Otherwise, the Cat objects will still be locked and won't be editable. It doesn't matter whether the Cat objects were created by client or by server. – fabiangebert Jun 06 '11 at 12:41