Common Action Class for many transactions. will it slow down the app performance?

[krishna kishore]

dear all,
i have a scenario like this... we have lots of transactions, all of which starts with choosing client, edit, modify etc. next from there will start the real transaction. we have kept a single common action class which serves as the client profile. depending upon the request the client page will serve, if next clicked forwards it to that specific transaction page.
now, the question is...
does this scenario of design slow down the performance of the application. because of a single resource providing support to lots of different transactions....

thanks in advance
-krishna

[Brent Sterling]

Hmmm...I thought I responded to this yesterday...maybe I forgot to submit my post.

I am curious why you think that using a common action class is a source of performance issues. What container are you using? I would think that your container would be able to handle multiple requests on separate threads that all used the same instance of your Action class. Isn't that the reason that action classes must be threadsafe?

- Brent