• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How to design a project archtecture

 
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Please forgive me if this is not a right forum for this question. I thought of this as most relevant

I am working on a project which is classified in to two independent web apps. Let’s say then project A and Project B. These both projects are being developed and maintained in separate SCM. Now I have got a requirement to share the project in infrastructure of project A. That means header and footer jsp pages of the project A will be same for the project B. When the header and footer projects are shared the data like user model (part of project A) is also need to be shared between projects. The main data shared between these projects is user name. When user navigates from a page of project A to a page in project B, He/she should see the welcome message in the header and relevant links in the Footer.

Please give me some insight about what are the options available for me to design my development and deployment architecture?

One solution I am thing is :

Create a Third Project for the common JSP pages and share that JSP files in both Project A and Project B.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic