Issue moved from:
https://sourceforge.net/tracker/index.php?func=detail&aid=1304577&group_id=36382&atid=416706
Consult the original issue for any attachments.
[ 1304577 ] Extension of the JRParameter interface
Submitted By: Rainer Langbehn - rlangbehn
Date Submitted: 2005-09-26 00:59
Last Updated By: rainerlangbehn - Comment added
Date Last Updated: 2005-12-03 22:53
Number of Comments: 4
Number of Attachments: 0
Assigned To: Nobody/Anonymous
Priority: 9
Summary:
Extension of the JRParameter interface
Please add the attribute "displayName" to the JRParameter interface along with Getter and Setter methods.
Why?
The calling application of jasperreports is responsible for presenting the required parameters and retrieving their actual values. In our, metadata driven, reporting
application we use the parameter metadata from the jasperreports reportdesign to create the parameter presentation.
To further support the report parameter presentation layer it would be very helpful, if the report parameter name would be of type JRExpression, to set the value by a java constant.
If you need help, I can do this for you. Thanks in advance.
Rainer Langbehn
norisbank AG, Germany
Comments
Date: 2005-12-03 22:53
Sender: rainerlangbehn
Logged In: YES
user_id=1055532
Hi Teodor,
parsing the parameter description is not the problem. We think, putting any parameter metadata into this free text tag is a bad design decision. It is obvious, that you will not get any support (validation, etc...) by a report designer tool into this.
We're planning to redesign our report parameter presentation to be absolutely generic and only driven by metadata from the reportdesign. Therefore it's absolutely necessary that the used report engine and any accompanying report design tool supports this concept. We don't agree that this would complicate the report template definition, 'cause it's only necesary to add some attributes along with getter and setter methods. The calling application of the report engine (jasperreports) is responsible for presenting the required parameters and retrieving their actual values, therefore the underlying report engine and any accompanying report design
tool must support this. We're also evaluating eclipse BIRT, which is much better
in this.
Rainer Langbehn
norisbank AG, Germany
Date: 2005-11-29 05:29
Sender: teodordProject Admin
Logged In: YES
user_id=332465
Hi,
I don't want to insist too much, but I think parsing the parameter description should not be such a big problem. The description could have the format of a property file, something like:
displayName=My Parameter
meaning=This parameter is used for something important
format=dd/mm/yyyy
allowedValues=
This parameter description containing this metadata could be parsed by creating a Properties object from the String value.
If we decide to add the displayName attribute to the parameter declaration, other users will want to see similar additional properties added and I just don't want
to complicate the report template definition. I hope this helps.
Teodor
Date: 2005-09-26 05:02
Sender: rlangbehn
Logged In: YES
user_id=1299031
Hi Teodor,
your suggested workaround is for us not possible, 'cause we're already using the tag for the localized parameter description, e.g. the meaning, format and allowed values. Mixing the displayName and the description needs any kind of parsing at runtime. That is not desirable.
I know that the requested change is not a trivial one. We can do this for you.
Thanks in advance.
Rainer Langbehn
norisbank AG
Date: 2005-09-26 02:47
Sender: teodordProject Admin
Logged In: YES
user_id=332465
Hi,
Are you already using the tag available for report parameters?
You could use this free text tag to store more information in a format recognizable by your application. You could put multiple things inside the parameter description and extract to accordingly at runtime.
Thank you,
Teodor
No Files Currently Attached
Recommended Comments