struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chughtai, Imran" <>
Subject RE: Re-usability of struts
Date Tue, 13 Nov 2001 16:46:21 GMT
We had to do the same, we need a user interface and a backend set of
reusable components.

We are using a layered approach and having all our reusable components as
Services (EJB) and Domain classes.
In our App, Struts calls a Service Method(EJB) which then calls a Domain
level class. The Domain classes contain all the main business logic. Domain
classes call the Persistence layer (DAO, CMP or BMP).

Our Action classes contain minimum code to call the EJB Methods.

This depends of the logic your User Interface is doing.

Might be overkill for your app but it seems like a good approach for us.


-----Original Message-----
From: Brandon Goodin []
Sent: 13 November 2001 16:50
To: 'Struts Users Mailing List'
Subject: RE: Re-usability of struts

I would like to hear some comments on this as well. Facing similar task.

-----Original Message-----
From: Jain, Sanjeev (GEAE, Foreign National)
Sent: Tuesday, November 13, 2001 9:19 AM
To: 'Struts Users Mailing List'
Subject: Re-usability of struts

Hi All,

We have an application ready in production which has used J2EE struts
framework. This application has the user interface to command it to perform
various calculations/actions and store the output in the database as well as
show it on the user screen.

Now, we are required to create another application which DOES NOT have an
user interface, everything is in back-end here. This application desires to
perform the same tasks as the previous application is doing. In other words
we are trying to automate the job which is done by the user in the first

Is it possible to reuse the code (struts objects) written in the first
application to enable the back-end process of the second application? If
yes, then how?


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message