We have a large enterprise application with approximately 6,000 users and a few hundred thousand lines of code. This app is working very well. We currently use Spring/Hibernate and annotations rather than hbm files. We are going through an exercise in refactoring our source code, dividing the source into multiple projects, with each project representing a specific functional module within the application. We have a large suite of unit tests attached to each module as well.
Problem we are running into is that the list of annotated classes/packages in our session factory bean is getting very long. We would like to divide it up into multiple files, one file per module and then reference (like an import) the various files from the sessionFactory config.
There are several goals that we are trying to achieve, two of which are organizational and long term ease of maintenance.
Any hints would be greatly appreciated.
|