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
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
The text was updated successfully, but these errors were encountered:
shannah
changed the title
Model (Entity) to/from json and in REST requests
RFE JSON encoding/decoding for models
Apr 28, 2020
This is on my list of things. The view models are designed to make conversion to other formats easy. I chose not to use PropertyBusinessObject because it wasn't quite right for the full scope of code rad. However I do plan to replicate all useful aspects of PropertyBusinessObjects, and provide easy versions to/from property business objects.
Until now I used a lot
PropertyBusinessObject
to store the data. I'm used to create the app database using almost onlyPropertyBusinessObject
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, theRequestBuilder
class offers method to send aPropertyBusinessObject
object as body request and to fetch aPropertyBusinessObject
object as the result of a request. At the moment, I consider thePropertyBusinessObject
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 thePropertyBusinessObject
class? How can I use the CoreRAD concepts while maintaining all the advantages of thePropertyBusinessObject
class in REST requests?Thank you
The text was updated successfully, but these errors were encountered: