Currently our system is based on CORBA. We have servlets in the presentation layer and CORBA/Java objects in the business tier. DB2 in EIS tier. We are having tough time in maintaing them as the Servlets contain HTML code. And Business tier is tightly coupled with Business logic and data access. So, decided to revise our architecture. Here is our new proposed architecture. 1. Presentation Tier. Use Struts Framework. 2. Business Tier. Use POJOs & Hibernate. Infrastructure: WebSphere Application Server. (All containers collocated on a single machine/JVM). My Questions: 1. Should we consider using EJBs instead of POJOs? 2. Should we introduce Session Bean facades to POJOs or let the presentation layer access POJOs directly? 3. Where do we implement Business logic? Session beans or POJOs? 4. How do we maintain User Session? Servlets or EJBs? 5. In future if we want to give access to remote clients, how do we do it? Thanks -Rancher
How many concurrent user do you expect? Is your business transaction intensive? Do you foresee 2 phase commits? What are your security requirements? The name police are going to rebuke you "rancher"...
Joined: Feb 02, 2004
Originally posted by Rufus BugleWeed: How many concurrent user do you expect? Is your business transaction intensive? Do you foresee 2 phase commits? What are your security requirements? The name police are going to rebuke you "rancher"...
=============================================== Users: 1000. Transaction intensive: No Two Phase Commit: No Security: As secured as possible. -Rancher
"Rancher" This post has been closed as it is a duplicate of this post in the EJB and Other J2EE Technologies forum. Your question is not relevant to those studying for the SCEA certification, so I have closed this thread. Please do not crosspost questions. And please change your displayed name to meet the JavaRanch Official Policy on Displayed Names. We need you to display a real name. You can change your displayed name here. Regards, Andrew