Posted By:
Ashutosh_Gupta
Posted On:
Monday, July 18, 2005 06:33 AM
Typically, a J2EE application contains 4 tier: 1. Client Tier 2. Web Tier (where jsps,the java classes typically used by JSP layer resides eg struts jar/controllers/DTOs/Form Classes) 3. Business Tier (session beans facade, mdbs, entity beans, persistant logic) 4. EIS/Database tier What I want to know, according to normal recommendations, should a call from web tier to business tier should always be a remote call? If we assume assume a typical J2EE installation would not have web tier on a separate box and business tier on a separate box (which is mostly the case). Then what is the rationale of using this approach? Is it normal to have a web tier class calling a EJB via local interface?
More>>
Typically, a J2EE application contains 4 tier:
1. Client Tier
2. Web Tier (where jsps,the java classes typically used by JSP layer resides eg struts jar/controllers/DTOs/Form Classes)
3. Business Tier (session beans facade, mdbs, entity beans, persistant logic)
4. EIS/Database tier
What I want to know, according to normal recommendations, should a call from web tier to business tier should always be a remote call? If we assume assume a typical J2EE installation would not have web tier on a separate box and business tier on a separate box (which is mostly the case). Then what is the rationale of using this approach? Is it normal to have a web tier class calling a EJB via local interface?
For creating a multi-tired application and integration purposes, we can expose only those APIs thru EJBs that we really want to expose through our application.
Any comments?
<<Less
