May 26th, 2006, 05:46 AM
I would take a look at AndroMDA:
Originally Posted by mail2bansi
Here is an intro article (all about layers, very easy to understand):
Also (more about layers, also very easy to understand):
Using AndroMDA with Spring and Hibernate (step by step tutorial):
If you don't work alone in your project, using AndroMDA will help you a lot by defining a clean architecture of your application, which can be followed by all developers rigorously. Another positive impact is that you won't care anymore of creating those XML (hbm, Spring XML, etc.). AndroMDA creates them for you :-)
Hope this helps!
May 26th, 2006, 07:48 AM
Tapestry is the presentation layer, which interacts with domain business interfaces. These domain interfaces obtain the implementation classes via Spring configuration and calls the persistant layer which is implemented in Hibernate.
The advantage of this architecture is that domain interface implementation can be changed via Spring configuration. Also database persistence layer can be switched without any code change. Another advantage of this architecture is that the domain implementation classes can be tested outside a Web application context. This architecture also supports declarative transaction management and web security model without the need for a EJB container. Overall, this architecture reduces the overall cost of developing enterprise application by reducing the cost of maintenance, cost application server licences and support cost. All the frameworks used in this application is open source and therefore it can be modified by in-house developers to support specific needs of an organisation