You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Eric Dalquist (JIRA)" <ji...@apache.org> on 2007/02/05 14:58:05 UTC

[jira] Created: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

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


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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "Eric Dalquist (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470415 ] 

Eric Dalquist commented on PLUTO-305:
-------------------------------------

So that would return a InternalPortletContext? That would work quite well.

Any plans on how to deal with the ClassLoader issues?

> 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.


[jira] Updated: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470429 ] 

David DeWolf commented on PLUTO-305:
------------------------------------

My bad, I was being an idiot :)

Even more of a reason to postpone until 1.1.1.  Thanks for getting me back on track.

> 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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470413 ] 

David DeWolf commented on PLUTO-305:
------------------------------------

Actually, I'll simply add a method:

getPortletContext(applicationId):PortletContext to the service.  This will provide access to everything you need (both the DD and the Context) without changing the api and without exposing internal interfaces.

> 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.


[jira] Updated: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ 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: 1.1.1
         Assignee: David DeWolf

> 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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "Eric Dalquist (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470426 ] 

Eric Dalquist commented on PLUTO-305:
-------------------------------------

Actually PortletContext doesn't seem to give us access to the ResourceBundles for each portlet in the context. The PortletConfig does that but that is PortletDD specific.

> 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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470417 ] 

David DeWolf commented on PLUTO-305:
------------------------------------

Actually, I'd rather return only the the PortletContext.  The implementation will probably happen to be the InternalPortletContext, but I don't think you should depend on that.  I'd rather not expose Internal interfaces unless I really need to.  Any reason why you need the internal?  You already have access to the dd and application id.

I'll take care of the class loader upon instantiation of the PortletContext (done from the PortletServlet.init).  Shouldn't be too messy.

> 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.


[jira] Commented: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470410 ] 

David DeWolf commented on PLUTO-305:
------------------------------------

I'm thinking that we could modify the PortletRegistryService to provide access to a composite (InternalPortletContext) of both the PortletDD and the PortletContext.  I'll be looking into this, but I think I'll probably push it off until 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
>             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.


[jira] Resolved: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

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

David DeWolf resolved PLUTO-305.
--------------------------------

    Resolution: Fixed

Let me know if this doesn't do the trick.


> 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.


[jira] Updated: (PLUTO-305) Provide access to a portlet's ResourceBundle's as loaded by Pluto

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ 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.1)
                   1.1.0

> 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.0
>
>
> 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.