If we need to test the Struts2's real performance we should not use database calls and stuff like that. The code should be as simple as possible, for example, as it was already suggested, we may use static data (a big enough list with beans that have at least 5 properties). We may include some logical part, for example, exclude beans with odd indexes to add a little functionality (we should notice that the bottleneck is in frontend/jsp/ognl side not in backend/actions side).
There were a question about how to test and how to measure the performance ... "jmeter" is a good choice. You may start jmeter with at least, for example, 20 concurrent clients, and set timeout to, for example, 1s. The more tests pass the better the performance is. Then you can decrease timeout and increase clients count. Best, Aram ________________________________ Aram Mkhitaryan 52, 25 Lvovyan, Yerevan 375000, Armenia Mobile: +374 91 518456 E-mail: [EMAIL PROTECTED]
