I like Display Tag a great deal, and the company I work for is using it activly.
However I was wondering if you have any plans to make it more Struts compliant, specifically with regard to the paging functionality :
1) The current parameter ecoding scheme used for paging and sorting of "d-" + table_name_checksum + "-" makes for invalid bean getters and setters on Struts ActionForm's, consequently I have to fish for them directly from the request in my Struts Actions.
Is there a reason they are encoded this way ?, or would it be possible to change the the scheme to "d" + table_name_checksum for example, so that Struts could handle setting/retrieving them through the Struts ActionForm?
2) There is no way to explicitly set a page from the tag in the JSP. i.e. If we want to set focus to a particular page because of what happened in the struts Action. The displaytag page is set to 1 or a value found in the request at present.
I have tried two approaches to overcome this problem : firstly modifying the request within the Struts Action to change the target page for a particular display tag table before control passes to the JSP's, but this causes difficulties with our Tiles mappings, and secondly modifying display tag itself by adding a page attribute to the table tag, which override's the parameter in the request when its value is > 0.
I don't like either of my solutions for the page setting problem and wondered if, in conjunction with the param encoding change, there was any mileage in suggesting that the scope that display tag used to search for paging parameters was widened to include Struts ActionForm's (or any other bean for that matter) within the page context.
Struts users would then be able to retrieve/modify the value of paging parameters from within their Actions as they normally do, by changing ActionForm properties.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Display Tag 1.0-b3 with Struts 1.1
I like Display Tag a great deal, and the company I work for is using it activly.
However I was wondering if you have any plans to make it more Struts compliant, specifically with regard to the paging functionality :
1) The current parameter ecoding scheme used for paging and sorting of "d-" + table_name_checksum + "-" makes for invalid bean getters and setters on Struts ActionForm's, consequently I have to fish for them directly from the request in my Struts Actions.
Is there a reason they are encoded this way ?, or would it be possible to change the the scheme to "d" + table_name_checksum for example, so that Struts could handle setting/retrieving them through the Struts ActionForm?
2) There is no way to explicitly set a page from the tag in the JSP. i.e. If we want to set focus to a particular page because of what happened in the struts Action. The displaytag page is set to 1 or a value found in the request at present.
I have tried two approaches to overcome this problem : firstly modifying the request within the Struts Action to change the target page for a particular display tag table before control passes to the JSP's, but this causes difficulties with our Tiles mappings, and secondly modifying display tag itself by adding a page attribute to the table tag, which override's the parameter in the request when its value is > 0.
I don't like either of my solutions for the page setting problem and wondered if, in conjunction with the param encoding change, there was any mileage in suggesting that the scope that display tag used to search for paging parameters was widened to include Struts ActionForm's (or any other bean for that matter) within the page context.
Struts users would then be able to retrieve/modify the value of paging parameters from within their Actions as they normally do, by changing ActionForm properties.