I was trying to export the display tag table data into a .pdf file using the latest code available in the SourceForce.net: Displaytag-1.2.jar library.
However i am getting an error while exporting to .pdf :
It Says abode reader could not open the .pdf file because it is either not a supported file type or because the file has been damaged(for example, it was sent as an email attachment and wasn't correctly decoded).
if the need to generate this &d-49653-e=5; at the end like that of link2. what do i do?
We’ve been able to narrow the problem down some more… We’re having a problem with displaytag rendering parameters in different orders. Our application uses both Spring Webflow, and Sitemesh. In order to export from displaytag, we added an exclude to the Sitemesh decorator.xml, that starts with our context path, and ends with the displaytag export parameter (“ourwebapp*-e-5”).
This approach worked fine on different servers… the spring flow execution key would appear before the displaytag export parameter. However, we’ve just run across other servers where it’s putting the displaytag export parameter in the center of the parameter string. We could modify our exclude, but there’s always the chance we may have the “-e=5” string generated by something else.
Is there a way to control the order displaytag generates the export URL?