I was wondering how far it is recommended to "keep" using struts when displaying information. Two examples might make it clearer about where I'm having trouble deciding.
For instance, I've got lots of forms on my site, I use Struts for all of them, love the extra functionality and the "one way of doing things" that Struts gives me. Then I have lots of "display information only"-pages. Most of these are tables that are based on some sort of DB table. Right now I: Call a struts Action. The Action retrieves the data, populates a boatload of Beans. The Beans are stuffed into a List, which in turn is put into a List which resides in my Form. The jsp retrieves the Form. The jsp performs a <logic:iterate id="bean" name="myForm" property="myList" indexId="i"></logic:iterate> The information is output with a lot of bean:write's Although this approach appeals to me in some ways (nice separation of concerns DB / Business-layer / Display for instance) it also seems a bit over the top at times. I could easily accomplish the same display by letting the .jsp do the talking with the DB. Or perhaps let a servlet do it all for me. My question is, do you guys use the above described method when only displaying information too ? Could this eventually become a performace bottleneck (maybe due the large amount of Beans being created) ? Is there perhaps a better variation of the above that I've missed ? All points of view welcome. //Linus Nikander - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
