You are viewing a plain text version of this content. The canonical link for it is here.
Posted to portalapps-dev@portals.apache.org by "Woonsan Ko (JIRA)" <ji...@apache.org> on 2010/04/01 17:38:33 UTC

[jira] Created: (APA-34) Support to set portletConfig based localization context for JSTL fmt tag usages.

Support to set portletConfig based localization context for JSTL fmt tag usages.
--------------------------------------------------------------------------------

                 Key: APA-34
                 URL: https://issues.apache.org/jira/browse/APA-34
             Project: Portals Apps
          Issue Type: Improvement
          Components: apa-demo, apa-gems
            Reporter: Woonsan Ko
            Assignee: Woonsan Ko
             Fix For: apa-demo-1.1, apa-gems-1.1


<fmt:setBundle/> tag in a jsp does not refer to portletConfig's resourceBundle.
So, the jsp cannot leverage the reloading feature of portlet resource bundle of portal.

One workaround is to use the following jsp scriptlet instead of using <fmt:setBundle .../>:

<%@ page import="javax.servlet.jsp.jstl.core.Config"%>
<%@ page import="javax.servlet.jsp.jstl.fmt.LocalizationContext"%>
<portlet:defineObjects/>
<%
Config.set(pageContext, Config.FMT_LOCALIZATION_CONTEXT, new LocalizationContext(portletConfig.getResourceBundle(renderRequest.getLocale())), 1);
%>

I think it would be better to support a convenient tag in apa-gems to do the same thing with a tag as follows:

<%@ taglib prefix="fmt-portlet" uri="http://portals.apache.org/applications/gems/fmt-portlet" %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
<fmt-portlet:setBundle/>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (APA-34) Support to set portletConfig based localization context for JSTL fmt tag usages.

Posted by "Woonsan Ko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko resolved APA-34.
---------------------------

    Resolution: Fixed

Fixed.

Also, one example is added into PickANumberPortlet of apa-demo.


> Support to set portletConfig based localization context for JSTL fmt tag usages.
> --------------------------------------------------------------------------------
>
>                 Key: APA-34
>                 URL: https://issues.apache.org/jira/browse/APA-34
>             Project: Portals Apps
>          Issue Type: Improvement
>          Components: apa-demo, apa-gems
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>             Fix For: apa-demo-1.1, apa-gems-1.1
>
>
> <fmt:setBundle/> tag in a jsp does not refer to portletConfig's resourceBundle.
> So, the jsp cannot leverage the reloading feature of portlet resource bundle of portal.
> One workaround is to use the following jsp scriptlet instead of using <fmt:setBundle .../>:
> <%@ page import="javax.servlet.jsp.jstl.core.Config"%>
> <%@ page import="javax.servlet.jsp.jstl.fmt.LocalizationContext"%>
> <portlet:defineObjects/>
> <%
> Config.set(pageContext, Config.FMT_LOCALIZATION_CONTEXT, new LocalizationContext(portletConfig.getResourceBundle(renderRequest.getLocale())), 1);
> %>
> I think it would be better to support a convenient tag in apa-gems to do the same thing with a tag as follows:
> <%@ taglib prefix="fmt-portlet" uri="http://portals.apache.org/applications/gems/fmt-portlet" %>
> <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
> <fmt-portlet:setBundle/>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.