Until now I used a lot PropertyBusinessObject to store the data. I'm used to create the app database using almost only PropertyBusinessObject objects. They are very convenient to exchange data with any external service, because they can seamlessly be converted to JSON and populated from JSON. Moreover, the RequestBuilder class offers method to send a PropertyBusinessObject object as body request and to fetch a PropertyBusinessObject object as the result of a request. At the moment, I consider the PropertyBusinessObject class as fundamental.
Your new CodeRAD model is very interesting, but it introduces a new way to store data in Entity objects. That makes sense, but do we lost all the advantages of the PropertyBusinessObject class? How can I use the CoreRAD concepts while maintaining all the advantages of the PropertyBusinessObject class in REST requests?
Thank you
Until now I used a lot
PropertyBusinessObjectto store the data. I'm used to create the app database using almost onlyPropertyBusinessObjectobjects. They are very convenient to exchange data with any external service, because they can seamlessly be converted to JSON and populated from JSON. Moreover, theRequestBuilderclass offers method to send aPropertyBusinessObjectobject as body request and to fetch aPropertyBusinessObjectobject as the result of a request. At the moment, I consider thePropertyBusinessObjectclass as fundamental.Your new CodeRAD model is very interesting, but it introduces a new way to store data in
Entityobjects. That makes sense, but do we lost all the advantages of thePropertyBusinessObjectclass? How can I use the CoreRAD concepts while maintaining all the advantages of thePropertyBusinessObjectclass in REST requests?Thank you