[ http://jira.codehaus.org/browse/DISPL-344?page=comments#action_65624 ]
Bill Joy commented on DISPL-344: -------------------------------- The export functionality is currently useless in the context of a portlet. And the solution proposed is that anyone who needs that feature must do his own custom extension to the container? I think it would be better to have export work within a portlet. Let the individuals who are designing a portlet decide for themselves whether the feature or total JSR 168 compliance is more important to them. > Export failure running as Liferay portlet > ----------------------------------------- > > Key: DISPL-344 > URL: http://jira.codehaus.org/browse/DISPL-344 > Project: DisplayTag > Type: Bug > Components: Export > 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 _______________________________________________ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
