Hi, We have very recently introduced NH in our product and are in the process of modularizing our product - the communication between two modules would be through services - In this process of restructuring we have not touched the table defenitions - as we have to support the old structure without NH and new structure with NH - while we are constructing the Domain Objects. The domain objects contain hierarchies. Since we have not touched the table defenitions it is possible that some of the columns in a table belong to a module and the remaining to another module. The question is how should we model the domain objects in this scenario. One of the thoughts is to build the domain objects containing only the relevant columns of the table, however this structure could lead to simulteneous updates on the same record set. Any thoughts or help would be appriciated
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhus...@googlegroups.com. To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
