Last year I was on a team that developed a complex ecommerce for T-Mobile
that used Struts 1.0.1 and EJB 1.1. We had the Action classes interfaced
with DAOs, which in turn went through a session façade (a single session
EJB) which in turn called some 40 different entity beans that, depending on
the function, either maintained state from the database or from a cache.
It's difficult to give you examples, but I can send you the source (it's
copyrighted, mind you).
Mark
-Original Message-
From: yan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 8:49 AM
To: [EMAIL PROTECTED]
Subject: Struts to EJB interface strategies
Hi,
Firstly, can anyone recommend a good resource that deals with how you
integrate a Web Tier implemented using Struts with the EJB Tier. And also a
resource that has an excellent example of how the Struts framework interacts
with J2EE. I am looking for more than the basic examples you normally find
as they do not help given the complexity of the application I am working on.
Secondly, what strategies does one use when deciding on how to implement the
ActionClass to Session Bean Inteface?
I am thinking along these lines:
Create a 'Client Helper Interface' that defines all the business methods
that your application will require. This Helper class will form the
interface between the ActionClasses and the Session Beans.
The ActionClass creates a 'Client Helper Interface' object and calls the
relevant methods within this interface. The Client Interface then creates a
Session Bean that implements the Client Interface.
The Session Bean creates the Entity Bean that opens the database connection
and returns the relevant data back to the Session Bean. The Session Bean
returns the required information back to the Client Helper Interface. The
Client Helper Interface returns to the ActionClass
Should you have a separate Helper Interface for each Session Bean?
many thanks
yan
KickStartESolutions - Intelligent Web Services [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
