java application architecture
Posted
by
LostMohican
on Programmers
See other posts from Programmers
or by LostMohican
Published on 2012-09-07T07:22:26Z
Indexed on
2012/09/07
9:49 UTC
Read the original article
Hit count: 182
java
|architecture
We have to write an administration panel for many customers. But we want to have just one administration panel, and use it in various projects.
This admin panel will have basic components such as access control logic, maker-checker system in changes, user logging and etc.
It will also have reporting for the customer, logs of transaction of the customer (which can vary according to the industry such as mobile banking, banking, ticket sales). These components may have to be modified according to the business.
So we are thinking about the architecture here, Is it OK to use jars of every basic components, and bring them together on a glue application? Or should we build each component as WARs and make interfaces between them?
If there are any more ideas, it will be appreciated.
© Programmers or respective owner