| Category: | Feature request |
Priority: | High |
Status: | Assigned |
| Project: | Severity: | Major |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
The default SUBREPORT_DIR was fine in the early releases of iReport & JasperReports, but I'm finding that each client I work for needs a more complex structure. This is because (1) the reports are developed and deployed in two different environments: Windows [iReport] and Unix [web application], respectively; and (2) we want to leverage reuse in subreports.
| Attachment | Size |
|---|---|
 parameter-packs.png | 18.65 KB |
1 Comment:
A "default set" of parameter packs could be assigned to a template template.
This way, when a developer creates a new report using a corporate template, they automatically get the default system pack and any other relevant packs. This has a number of other advantages:
- The name of the parameter pack becomes its name space. (Prepend the pack name to avoid conflicts.)
- The interface will be cleaner for new users.
- Redundancy can be eliminated from parameter names.
- Reuse packs between master and subreports. (Makes it more efficient to pass parameters: drag and drop the pack onto a subreport.)
Parameter packs also open up the possibility of having the master report automatically pass the parameters to subreports. That is, if a subreport has a parameter pack whose name and parameter names match the master report, there is no need to force the developer to link them up. The system can do this at runtime.