Project Architecture For Enhancing Legacy project.
Posted
by vijay.shad
on Stack Overflow
See other posts from Stack Overflow
or by vijay.shad
Published on 2010-03-20T16:04:27Z
Indexed on
2010/03/20
16:11 UTC
Read the original article
Hit count: 410
legacy-code
|architecture
I am working on legacy project. Now the situation demands project to be divided into parts. What strategy I should follow to do this task.
Description:
The legacy project (A) is fully functional web application with almost well defined layers. But now i need to extend the project to a further enhancement. This project usage maven as build tool. But it is used only for dependency managements only. (project exported to war form inside eclipse).
The new enhancement needs me to add new data table, new UI(jsp, css, js and images).
What should be my strategy to enhance to application.
My proposed design.
I am planing to create two new projects
Project B : Main Enhancement works will done in this project. Will have all layers like service layer, dao layer and UI layer in itself. And will be a web application in itself.
Project C : Extract some common model and service code form project-A and create this project. This project will be added as dependency to both the projects.
If my this approach is okay! Then i presume there will be problem be problem in deployment. These two projects will demand to deploy separately(currently tomcat is used). But I must deploy these two projects as one war. So, i need to have a plan to change the web.xml entries to have configurations for both projects. This will comes with some more complexities with project.
What should be my design for the project? Does my plan sounds good.
© Stack Overflow or respective owner