The solution options are as follows:
- The logical separation of the application into different tiers (client, presentation, business logic, integration and EIS tier) allows a system to be flexible and easily maintained. When there are any changes in presentation, it will be done at the presentation tier, and it will not affect the other tiers. If there are any business logic changes, only EJB component business logic get changed, and it will not affect other tiers, and vice versa.
- MVC pattern leverages command patterns at the web tier (JSF backing bean classes) for handling web events. Therefore, when new functionalities are added to the system, it will not affect the existing system. We can easily create a new web action ...