[ http://jira.codehaus.org/browse/DISPL-344?page=comments#action_76580 ] Kelly Graves commented on DISPL-344: ------------------------------------
Eric, Well I ran into some problems with Vignette. It seems that when placing data into the session from a portlet (application scope) they actually use undocumented wrapper classes for the attributes stored making it impossible for me to pull this data out from a web-app servlet. This obviously is not adhering to the spec so I am going to open a ticket with Vignette. What I am doing in the meantime... - Created a web-app servlet that re-queries for the same data set as portlet. New servlet forwards to a new JSP that includes the same display:table tag as was used in the original portlet jsp (but wouldn't necessarily have to.) - In the html for the original portlet JSP, i include custom export links for the user that pass the necessary request parameters to cause the new servlet+jsp to respond directly with the pdf or excel version. - Set up the ResponseOverrideFilter for the new servlet. - Had to modify PortletRequestHelperFactory.java - Since when processing directly from the web-app, PortletRequestHelper is expecting to find the javax.portlet attributes, which are not present. So I had to put in a check in the Factory to fall back to the regular RequestHelper in this case. Can't set the Factory property from within the tag, so can't switch it based on the context I'm in. Things are working fine at present. I'll keep you posted... Kelly > Export failure running as Liferay portlet > ----------------------------------------- > > Key: DISPL-344 > URL: http://jira.codehaus.org/browse/DISPL-344 > Project: DisplayTag > Issue Type: Bug > Components: Export > Affects Versions: 1.1 > Reporter: Bill Joy > Priority: Blocker > Attachments: Capture-05-18-00001.png > > > When click on any of the Export options, the content of the portlet is > replaced with the exported data. > If do not add the "displaytag extensions" for JSR 168 portlet support, the > export feature works correctly. > I consider this a blocker because without the portlet extensions the > "pagesize" table attribute has unacceptable behavior (so I have to choose > which feature I prefer to enable). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
