I know that the topic of passing parameters to decorators has come up before. It seems that the best solution was to pass values through the PageContext.
>From a look at the code, it seems to me that one could declare an ad-hoc parameter using the <display:setProperty> tag. A TableDecorator has access to the effective TableModel. Within the TableModel, one can find the TableProperties, where the ad-hoc property has been defined. The problem is in getting the ad-hoc parameter from the TableProperties... All the exposed property getters seem to be convenience methods to simplifier property retrieval. There is a general getProperty(String) method; however, its scope is private. Would it be feasible to make the getProperty(String) method public so that the TableProperties object facilitate parameterized TableDecorators? Is there some fundamental reason this method was made private to begin with? Thoughts? I think that I am going to get a copy of the code from Subversion and test my ad-hoc parameter idea... Will keep you posted... Thanks, Jon -- Jon Brule tricolorcat-at-gmail.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ displaytag-user mailing list displaytag-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-user
