This is an exported version of the JIRA issue tracker. Please use the Google Code site to open new tickets or report updates to these existing tickets. Feel free to contact the mailing list with any questions.

[RRR-44] Need to be able to choose resources from a list
Created: Mon, 6 Dec 2004 14:32:26 -0800 (PST)  Updated: Tue, 7 Dec 2004 16:42:01 -0800 (PST)

Status:Closed
Project:ReportRunner
Component/s:Web Wizard
Affects Version/s:0.3
Fix Version/s:0.3

Type:ImprovementPriority: Major
Reporter:Henri YandellAssignee:Henri Yandell
Resolution:Fixed 
Environment:


 Description   
Rather than just having a report run on only one resource, it should be able to run against a list of options. Currently thinking that the resource attribute of a report would look something like:

resource="JiraDS or ConfluenceDS".

This won't scope well when people want to run a report that uses two resources though.

***

It's a param! Doh :) Though it has to be answered before the param page can, so maybe a new tag: <resource-param name="SqlReportDS" options="JiraDS,ConfluenceDS,RollerDS"/>

This scopes nicely and can even replace the resource attribute of the report tag:

<resource-param name="SqlReportDS" value="JiraDS"/> would replace resource="JiraDS" in report tag.
Comment by bayard [ Mon, 6 Dec 2004 18:02:22 -0800 (PST) ]
Half coded, and now needs recoding.

The <resource-param> should be a part of a ReportGroup, not a Report.

The Resource should use reflection to be set on the report. So SqlReport should have setSqlReportDS() as a method.

The report xml may need nothing resource-wise...ponder.

The jsp choice should happen in the same place as currently, ie) after the report is chosen.
Comment by bayard [ Tue, 7 Dec 2004 16:42:01 -0800 (PST) ]
This is implemented. Bit of cleanup to do, but I'll make that a new issue. The use tag needs to die in the reportrunner.xml and should just be a resource-param without options.