Add export/import portletcontext support to the PortletInvoker -------------------------------------------------------------- Key: GTNPC-26 URL: https://jira.jboss.org/browse/GTNPC-26 Project: GateIn Portlet Container Issue Type: Feature Request Reporter: Matt Wringe Attachments: export-import-PortletInvoker.patch As part of the wsrp 2.0 specification, there is a mean to export a portlet and then import it back into a server (which may or may not be the same server). In order to implement this we need to be able to retrieve the portlet handle (ie portlet ID) and portlet states from the PortletInvoker. There are a few changes which would need to be added to the PortletInvoker interface to allow for this to happen: - provide access to the state of a portlet. The invoker doesn't necessarily provide a means to retrieve this since it can store the state locally and not passed as part of the portlet context. - provide a means to access the portlet id of the original non-cloned portlet. We may need to export a cloned portlet into a server which doesn't have that particular clone (or the clone on the original portal may have been deleted). We should add an export method to the PortletInvoker interface to export a portletcontext suitable for export, and an import method which will create a new portlet based on this value.

Add export/import portletcontext support to the PortletInvoker -------------------------------------------------------------- Key: GTNPC-26 URL: https://jira.jboss.org/browse/GTNPC-26 Project: GateIn Portlet Container Issue Type: Feature Request Reporter: Matt Wringe Assignee: Matt Wringe Fix For: 2.2.0-Beta01 Attachments: export-import-PortletInvoker-improved-with-tests.patch, export-import-PortletInvoker.patch As part of the wsrp 2.0 specification, there is a mean to export a portlet and then import it back into a server (which may or may not be the same server). In order to implement this we need to be able to retrieve the portlet handle (ie portlet ID) and portlet states from the PortletInvoker. There are a few changes which would need to be added to the PortletInvoker interface to allow for this to happen: - provide access to the state of a portlet. The invoker doesn't necessarily provide a means to retrieve this since it can store the state locally and not passed as part of the portlet context. - provide a means to access the portlet id of the original non-cloned portlet. We may need to export a cloned portlet into a server which doesn't have that particular clone (or the clone on the original portal may have been deleted). We should add an export method to the PortletInvoker interface to export a portletcontext suitable for export, and an import method which will create a new portlet based on this value.