Porperties that are not in view are set to NULL on dataContext commit

Support
#1

There is a problem with load() method and data containers commit in which after the load() method is called once to load a certain collection, the data container will be loaded with all the properties even though the view set on the corresponding data container does not contain all those properties. I believe there has something to do with the dataContext merge in the load() implementation.

Before the load method is called, if I try in debugger to fetch a property which is not present in the view, it throws [IllegalStateException: Cannot get unfetched…] which is ok, but after the load() method is called, when I try to fetch the same property it does not throw any errors and it shows the current value of the property, which is not ok.

We have a VERY BIG PROBLEM in our enterprise solution where properties are set to null and persisted into the database. If the entity is passed to the service layer after a call of the method load(), on the next dataContext commit the value of null is set to all those properties that are not present into the view of the data container in the xml descriptor. That means we should always include all the properties into the view, which kind of defies the purpose of views.

I have extended the cuba-petclinic project with services and a Status property on the Person entity to be able to show the problem. I have also made a video where you can see how the Status property on the Employee is being set to null after editing the entity twice (on the second edit dataContext.commit() persist null on properties, after the load() method is called in first edit).

cuba-petclinic-issue.zip (7.5 MB)
https://drive.google.com/open?id=1h920R21LTl4O7LYbt7u-ENVmS6TylzbO

3 Likes
#2

Hello @radugavenea

Could you clarify what version of CUBA do you use?

Regards,
Daniil

#3

I am using the latest Cuba plugin in Intellij IDE. It says version 12.3-191

#4

I’m talking about CUBA framework, not CUBA Studio. You can find the version in the project properties window

#5

Sorry about that. We currently use cuba 7.0.9, but the demo petclinic example I’ve added is using 7.1.2.

#9

Thank you for the report, I have filed an issue.
Until it is resolved, you can work around the problem by clearing the DataContext right after commit and before loading it again:

dataContext.commit();
for (Entity entity : ((DataContextImpl) dataContext).getAll()) {
    dataContext.evict(entity);
}
employeesDl.load();
2 Likes
#10

Hello @knstvk,

Happy new year!
I saw that the issue should be fixed for platform versions 7.1.4 and 7.2.0.

I tried 7.1-SNAPSHOT which normally should point to 7.1.4 but the issue is still there.
Am I missing something?

Thanks,
-c

1 Like
#11

Hi @codrin,

Yes, the issue should be fixed in 7.1-SNAPSHOT.
We’ll double-check before releasing 7.1.4.

Regards,
Konstantin

1 Like
#12

Hello @knstvk,

I’ve look into the issue and I have to say is not completely fixed.

It’s been solved for subsequent commit and merge calls. So it works for edit, but still does not work for remove.
If you have subsequent calls of commit and remove, on the second commit call information is still lost.

dataContext.remove(entityDc.getItem());
dataContext.commit();

Thanks,
Radu

1 Like
#13

Hi Radu,

Unfortunately, I couldn’t reproduce the problem on my tests.
Could you provide more information? What steps lead to the problem?
What information is lost? References in the removed entity?