GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm Attachments: UIPortlet.gtmpl GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value.

GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm Fix For: 3.2.0-GA Attachments: UIPortlet.gtmpl Original Estimate: 4 hours Remaining Estimate: 4 hours GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value.

GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm Assignee: tung do thanh Fix For: 3.2.0-GA Attachments: UIPortlet.gtmpl Original Estimate: 4 hours Remaining Estimate: 4 hours GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value.

GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm Assignee: tung do thanh Fix For: 3.2.0-GA Attachments: 2010-08-02-GTNPORTAL-1382.patch, UIPortlet.gtmpl Original Estimate: 4 hours Remaining Estimate: 4 hours GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value.

GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm Assignee: tung do thanh Fix For: 3.2.0-GA Attachments: 2010-08-02-GTNPORTAL-1382.patch, UIPortlet.gtmpl Original Estimate: 4 hours Remaining Estimate: 4 hours GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value.