[ http://jira.codehaus.org/browse/DISPL-344?page=comments#action_65625 ]
Eric Dalquist commented on DISPL-344: ------------------------------------- What I was trying to say is there is no way to implement exporting that will work in more than one portal container. I could get export working in uPortal, using custom extensions to the portlet specification that uPortal has implemented. This export functionality would be tied to uPortal and not work in another portal unless it provided the same extensions. Liferay likely has some extentions to the spec as well and export could be implmented to work in that portal but again, it would be specific to that portal. I was not implying there is a portal agnostic way to do it but we shouldn't implement it because the spec doesn't support it. I'm implying there is no way to implement export of binary content from a portlet that will work on every portal container at this point in time. This is a shortcoming of the JSR-168 specification that will hopefully be addressed in version 2 of the spec which is in progress. That being said if you are interested uPortal's method of allowing binary content to be rendered may be doable in liferay as well. uPortal has a custom WindowState called Exclusive in which a portlet has complete control of the output stream and can set any content type for the result. If this sounds interesting I could probably give some direction in implementing export functionality to use this feature for the displaytag library. > 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
