I canโt speak for Java people, but on the .NET side of things, I believe that mapping files can be split (xml files describing the relationship between the database and objects).
Other than that, what would you like to share? Do you think about business logic? Please define "share logic" a little further.
You could have your Java people write the persistence code and display it as RESTful services, then .NET Windows GUI programmers could just code it ... or vice versa.
Ultimately, there shouldn't be much Hibernate / nHibernate code, since for it you no longer need to write such a data access code. All that remains is the application logic with minimal interaction with (n) Hibernate, which will differ depending on your language.
source share