Originally posted by jiju ka:
Is it a must for your application to have value Objects (beans) to represent each tier?
If the mappings changes often you can have your mappings stored in a file. May be xml file.
Mappings will have the relation ships between Presentation layer Beans and Business Layer Beans. Mapping can have relation ship between Business Layer and Persistence layer too.
Originally posted by Stan James:
You emphasis on project dependencies is good. It would also work to think about compilation or deployment units rather than IDE projects. Can you deploy a new release of X without breaking Y? Can you change the interface between X & Y without also changing Y & Z?
I wonder if you could make the objects exposed by the business layer to the presentation layer extend the objects exposed by the persistence layer to the business layer. Presentation has no dependency on the presistence classes; the business can break that extends relationship if it needs to diverge to a new structure.
BTW: In my work life, the projects are vertical containing all the classes for one product or user group through all layers of the architecture. All the projects depend on one core project, but almost none depend on each other.
[ December 09, 2005: Message edited by: Stan James ]
more than one persistence technology in the whole project