Greetings,
Thanks Mr Craig and Mr Niall.
Yes we are having sub application modules and we are having one common action Class for some action mappings (design based on struts-scaffold - Refer: Struts In Action).I have to check it whether it is for module or for application. Actually What we thought is minimum number of same action class instance will serve for maximum number of requests. That is for example, if ten action elements are mapped to the same action class, in less user traffic, five action instance is enough to serve, need not create ten instance of the same action class. (but I think the struts specification is slightly different)
Niall was correct on this, by the way, but so was I (sort of :-). If you have an <action> element specifying the same Action class in two modules, you'll get two instances.
As others have pointed out, your Action classes need to be able to handle multiple simultaneous requests -- there is no locking going on, so there is no performance penalty for sharing. Most importantly, that means you should avoid using instance variables in your Action classes to store things that are specific to an individual request -- use local variables inside your methods and most of the potential problems of simultaneous requests go away, since the JVM will create those variables on the stack associated with each request thread.
Rgds,Craig
Sen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
