While this is probably good enough for a simplistic dashboard-type portal,
it??™s clearly not good enough to be a more robust report portal like you??™d want in a true
enterprise environment. So, one suggestion is to allow for parameters to be entered and
used by the report. This will require parsing the report XML (using Commons Digester
perhaps?) and looking for the parameters (explore the DataVision report format; it??™s not
very complicated at all). You??™ll most likely want to add a getReportParameters() method
to the ReportRunner class, which will be called when the user clicks a report from his or
her favorites. This should return a List of ReportParamDescriptor objects, and you can
then use this list to generate an HTML form the user can fill out. Collect the parameters
and pass them along to the runReport() method. The details of using parameters with
DataVision reports programmatically can be found in my article on using DataVision in
a web application here: www.omnytex.com/articles. You??™ll find that it amounts to not
much more than one or two simple method calls on the Report object. This may sound
like a lot of work, but I think you??™ll find it??™s really not too much, and it??™ll definitely get
you some more experience with DWR, not to mention DataVision.
Pages:
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716