You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... as well as Object creation, which is per POJO/bean instance, currently.
Currently, a BeanModel object hierarchy is created for each instance of an Object (Class) type / POJO. Rather, it would be ideal if the BeanModel object hierarchy only needed to be created per Object (Class) type, not per instance.
Unfortunately, the way the Property (model) class was designed, it depends on the Object instance to get and set property values. Therefore, there needs to be clearer separation between model and instances of the model structure.
The text was updated successfully, but these errors were encountered:
jxblum
changed the title
Refactor Elements JavaBeans Model classes and optimize memory consumption
Refactor Elements JavaBeans model classes and optimize memory consumption
Oct 29, 2022
... as well as Object creation, which is per POJO/bean instance, currently.
Currently, a
BeanModel
object hierarchy is created for each instance of an Object (Class) type / POJO. Rather, it would be ideal if theBeanModel
object hierarchy only needed to be created per Object (Class) type, not per instance.Unfortunately, the way the
Property
(model) class was designed, it depends on the Object instance to get and set property values. Therefore, there needs to be clearer separation between model and instances of the model structure.The text was updated successfully, but these errors were encountered: