Details
Improvement
Open
Major
Description
When using Displaytag along with Sitemesh, exports are being decorated via Sitemesh, which is expected. In order to get correct exports, I currently have to show the entire result on one page (non paging/sorting) and set a the table's requestURI to a value I exclude from Sitemesh decoration.
It would be helpful to allow end users to define an optional requestURI for exports. Then users coudl tell sitemesh to not decorate that url.
Another option is to add another export paramter, aside from the current "d-*-e" parameter that gets appended. Something like, "&display_exporting=true". This would allow Sitemesh users to map a blank decorator to url's with this parameter.
It would be helpful to allow end users to define an optional requestURI for exports. Then users coudl tell sitemesh to not decorate that url.
Another option is to add another export paramter, aside from the current "d-*-e" parameter that gets appended. Something like, "&display_exporting=true". This would allow Sitemesh users to map a blank decorator to url's with this parameter.
A possible work-around solution is to put into the sitemesh decorators.xml file, section <excludes> the pattern *d-*-e*
This will allow the exports not to be decorated but it will decorate the displaytag paging (which is based on pattern "d-*-p").
Doing this you can use both paging and exports with displaytag and sitemesh.