Thom Burnett wrote:
There is controller already ;-) ActionServlet is a controller which dispatches requests to Action classes. So it does not make any sense to create another one.My question is, what's the recommended practice. Is it considered best to keep different actions for each major purpose or to have one Action (controller) sorting and dispatching incoming requests.
-- Mikolaj Rydzewski <[EMAIL PROTECTED]>
smime.p7s
Description: S/MIME Cryptographic Signature
