You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bridges-dev@portals.apache.org by "Woonsan Ko (JIRA)" <br...@portals.apache.org> on 2007/10/26 07:38:50 UTC
[jira] Resolved: (PB-75) GroovyPortlet need to support Jetspeed's
new feature, auto-dispatching for edit_defaults mode option.
[ https://issues.apache.org/jira/browse/PB-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Woonsan Ko resolved PB-75.
--------------------------
Resolution: Fixed
Fixed.
So, now every bridge-based portlet can support edit_defaults mode if it support only edit mode.
By the way, I'd like to mention about Spring Portlet MVC based portlet on Jetspeed-2.
Because it does not support public doEdit() method, so we can do the following workaround:
If a Spring Portlet MVC based portlet has the following portlet mode mappings:
<bean id="portletModeHandlerMapping" class="org.springframework.web.portlet.handler.PortletModeHandlerMapping">
<property name="portletModeMap">
<map>
<entry key="view"><ref bean="myPortletViewController"/></entry>
<entry key="edit"><ref bean="myPortletEditController"/></entry>
<entry key="help"><ref bean="myPortletHelpController"/></entry>
</map>
</property>
</bean>
If you want the portlet to support edit_defaults mode, then just add the following:
<entry key="edit_defaults"><ref bean="myPortletEditController"/></entry>
That is, just copy from "edit" mode configuration and rename the key with "edit_defaults".
> GroovyPortlet need to support Jetspeed's new feature, auto-dispatching for edit_defaults mode option.
> -----------------------------------------------------------------------------------------------------
>
> Key: PB-75
> URL: https://issues.apache.org/jira/browse/PB-75
> Project: Portals Bridges
> Issue Type: Improvement
> Components: groovy
> Affects Versions: 1.0.3
> Environment: Jetspeed-2.1.3
> Reporter: Woonsan Ko
> Assignee: Woonsan Ko
> Priority: Minor
> Fix For: 1.0.4
>
>
> When Jetspeed 2's auto-dispatching for edit_defaults mode option is turned on, JS2 would try to invoke doEdit() method directly without invoking render() method.
> For this functionality, Jetspeed-2 tries to know if the portlet is extending GenericPortlet and if it has public doEdit() method. (See https://issues.apache.org/jira/browse/JS2-634 for details.)
> However GroovyPortlet does not extend GenericPortlet, differing from other bridges. So, this new feature would not work for Groovy portlets.
> Therefore, GroovyPortlet need to extend GenericPortlet and have public doEdit() method to support the new feature of JS2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org