how much business logic should i put into actions?

[Rivka Shisman <ri...@nite.org.il>]

Hi friends,

 

I am developing a web application in which I have struts that call EJB
that uses other utility java classes.

I started to wonder - how much business logic should I put into struts
Actions?

 

For example, if I'm creating a report with jasper reports - should the
report creation be on the EJB level or the struts Action level? From
what I saw in the mailing lists most programmers put the report creation
logic in Servlets?

 

I'll be very thankful to see your thoughts about that

 

Thanks

Rivka

 

 

RE: how much business logic should i put into actions?

[Mark Benussi <ma...@hotmail.com>]

I would create a Manager class to do any business logic, that sits between 
your Action and EJB.

This exposes this functionality to any other layers (Other than the web) 
that may wish to use the functionality for instance a Thick Java Client

----Original Message Follows----
From: "Rivka Shisman" <ri...@nite.org.il>
Reply-To: "Struts Users Mailing List" <us...@struts.apache.org>
To: "Struts Users Mailing List" <us...@struts.apache.org>
Subject: how much business logic should i put into actions?
Date: Wed, 14 Dec 2005 12:40:47 +0200

Hi friends,



I am developing a web application in which I have struts that call EJB
that uses other utility java classes.

I started to wonder - how much business logic should I put into struts
Actions?



For example, if I'm creating a report with jasper reports - should the
report creation be on the EJB level or the struts Action level? From
what I saw in the mailing lists most programmers put the report creation
logic in Servlets?



I'll be very thankful to see your thoughts about that



Thanks

Rivka



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org