Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is our behavior for transience ok? #19

Open
mhgrove opened this issue Feb 19, 2010 · 1 comment
Open

is our behavior for transience ok? #19

mhgrove opened this issue Feb 19, 2010 · 1 comment
Milestone

Comments

@mhgrove
Copy link
Owner

mhgrove commented Feb 19, 2010

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.

@mhgrove
Copy link
Owner Author

mhgrove commented Sep 29, 2010

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.

@mhgrove mhgrove modified the milestones: 0.9, 1.0 Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant