[JBoss JIRA] Created: (GTNPC-26) Add export/import portletcontext support to the PortletInvoker
by Matt Wringe (JIRA)
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
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (GTNPORTAL-1400) RestResource can't get parameter when submit with http post or put method
by Vu Viet Phuong (JIRA)
RestResource can't get parameter when submit with http post or put method
-------------------------------------------------------------------------
Key: GTNPORTAL-1400
URL: https://jira.jboss.org/browse/GTNPORTAL-1400
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Vu Viet Phuong
Assignee: Vu Viet Phuong
Fix For: 3.2.0-GA
when i test @Managed, @Impact(ImpactType.IDEMPOTENT_WRITE) which currently used to expose some service's methods, i found some problems:
- Rest mehods without parameter OR exposed with @Impact(ImpactType.READ) is called as expected
- Rest methods with parameter AND exposed with @Impact(ImpactType.IDEMPOTENT_WRITE) or @Impact(ImpactType.WRITE) can't be called properly
That the problem of org.exoplatform.management.data.RestResource class. Currently, this class determine the exposed methods by using method name and their parameters, but now it just can retrieve parameter values from QueryString
If i expose a method that need POST http method, and parameters is transfered to server in the HttpRequest's InputStream, not in the QueryString , RestResouce can't retrieve the parameter values and the exposed method can't be called
I've attached the patch to fix this issue
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months