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
we read from the db and populate the object, but we don't persist. i think that's useful because it gives you readonly properties.
however, hibernate and probably others, dont read either. so our implementation is different, which is probably not desireable. do we keep the different implementation and document it in bold letters, or add a @readonly annotation, or something similar, implement transient the same way as everyone else, and be done with it. i like having my cake and eating it too, but i also dont want to add more non-JPA annotations if avoidable.
this is probably a punt until people actually start using empire.
The text was updated successfully, but these errors were encountered:
the suggestion on the mailing list is the way to go, in the face of missing RdfProperty annotations, try and create the property based on the name of the field/property & the namespace the instance is a part of. If that doesn't work, oh well. but this get's the same behavior people would expect from normal JPA systems, which i think is good.
we read from the db and populate the object, but we don't persist. i think that's useful because it gives you readonly properties.
however, hibernate and probably others, dont read either. so our implementation is different, which is probably not desireable. do we keep the different implementation and document it in bold letters, or add a @readonly annotation, or something similar, implement transient the same way as everyone else, and be done with it. i like having my cake and eating it too, but i also dont want to add more non-JPA annotations if avoidable.
this is probably a punt until people actually start using empire.
The text was updated successfully, but these errors were encountered: