[
https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David DeWolf updated PLUTO-305:
-------------------------------
Fix Version/s: (was: 1.1.0)
1.1.1
Oops. partially supported in 1.1.0, full support will be in 1.1.1.
> Provide access to a portlet's ResourceBundle's as loaded by Pluto
> -----------------------------------------------------------------
>
> Key: PLUTO-305
> URL: https://issues.apache.org/jira/browse/PLUTO-305
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 1.1.0
> Reporter: Eric Dalquist
> Assigned To: David DeWolf
> Fix For: 1.1.1
>
>
> A service is needed to access the ResourceBundle of a a portlet for a
> specific Locale. Since Pluto is already dealing with classloaders to load the
> portlet's ResourceBundle's as they are requested from the PortletConfig API.
> The part of this enhancement that will be more difficult is dealing with
> ResourceBundle requests from the portal for a ResourceBundle that has not yet
> been loaded. The portal shouldn't need to provide a full request/response
> context so Pluto will need a way other than getting the context class loader
> from the current thread to load the ResourceBundles.
> One option would be to store the ClassLoader for the PortletDD somewhere when
> the init() call is made to the portlet.
> Another part of the enhancement that is difficult to answer is how the portal
> should identify which PortletDD it wants to get a ResourceBundle for. The
> requested API is along the lines of:
> ResourceBundle resourceBundleService.getResourceBundle(Locale,
> PortletDDIdentifier);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
