Linus Nikander wrote:
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.
This raises an interesting point, which I've not run into yet.
This is often solved in a non-Struts application by having a "reporting" facility which is used to do the analysis/pure-display pages (i.e. ones which have minimal interaction with the rest of hte application, but which create a lot of heavy-lifting reports). That facility is often provided by a third-party package such as Crystal Reports.
Does anybody have any experience integrating a Struts application with a third-party package like that? Any tips? I'm curious because some of the stuff I work on may have that type of requirement (big report pages) in the future, and we've got people that are experienced with Crystal Reports, so if I can easily integrate that into the technology stack I'd love to.
Kirk Wylie M7 Corporation
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
