I have started a Blog on how to keep a Domain Model free of persistence logic (http://ricbrown.blogspot.com/2004/09/transparent-persistence-paradox.html).
I was wondering how Jaxor handles keeping persistence logic out of the Domain Model when the domain logic needs to search a large collection of elements (e.g., to check that a property is unique)?
Regards,
Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Through code generation, Jaxor is able to generate all persistence related data. With other O/R approaches, developers code the bean fields which are directly related persistence through the mapping document.
Hello,
I have started a Blog on how to keep a Domain Model free of persistence logic (http://ricbrown.blogspot.com/2004/09/transparent-persistence-paradox.html).
I was wondering how Jaxor handles keeping persistence logic out of the Domain Model when the domain logic needs to search a large collection of elements (e.g., to check that a property is unique)?
Regards,
Richard
Through code generation, Jaxor is able to generate all persistence related data. With other O/R approaches, developers code the bean fields which are directly related persistence through the mapping document.
You can read more about the separation here:
http://jaxor.sourceforge.net/?q=domain