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 "Nikita Dubrovsky (JIRA)" <ji...@apache.org> on 2008/05/15 20:34:56 UTC
[jira] Created: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: PLUTO-488
URL: https://issues.apache.org/jira/browse/PLUTO-488
Project: Pluto
Issue Type: Improvement
Components: portlet container
Affects Versions: 1.1.5
Environment: Tomcat 5.5.26
Reporter: Nikita Dubrovsky
Priority: Trivial
A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-488:
--------------------------------
Fix Version/s: 2.0.0
Thanks for the patch Nikita. I will commit it in a day or two. I think that this issues is also present in the Pluto 2.0 codebase, but the PortletContainerImpl class is very different from the file in the 1.1.x branch. Is it possible that you could produce a patch for the trunk too? TIA
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615093#action_12615093 ]
Craig Doremus commented on PLUTO-488:
-------------------------------------
Added P488-trunk-Rev670645.diff patch to trunk in SVN rev 678278. Thanks Nikita!
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff, P488-trunk-Rev670645.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-488:
--------------------------------
Affects Version/s: (was: 1.1.5)
2.0.0
Fix Version/s: (was: 1.1.6)
Patch applied in SVN rev 661639 to 1.1.x branch..
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus resolved PLUTO-488.
---------------------------------
Resolution: Fixed
Patch applied to trunk and 1.1.x and pluto-2.0-refactoring branches.
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff, P488-trunk-Rev670645.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Nikita Dubrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Dubrovsky updated PLUTO-488:
-----------------------------------
Attachment: P488-1.1.x-Rev656347.diff
Attached a patch with the proposed fix (modified PortletContainerImpl).
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Nikita Dubrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Dubrovsky updated PLUTO-488:
-----------------------------------
Fix Version/s: 1.1.6
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Nikita Dubrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602383#action_12602383 ]
Nikita Dubrovsky commented on PLUTO-488:
----------------------------------------
I have never worked with Pluto 2.0 yet, but I will take a look next week (I am on vacation for the next 4 days :) and should be able to create a patch for it. Thanks for applying the patch!
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615136#action_12615136 ]
Craig Doremus commented on PLUTO-488:
-------------------------------------
Applied P488-trunk-Rev670645.diff patch in rev 678334 and 678336.
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff, P488-trunk-Rev670645.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Nikita Dubrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Dubrovsky updated PLUTO-488:
-----------------------------------
Attachment: P488-trunk-Rev670645.diff
Attached a patch for Pluto 2.0. Instead of modifying the individual methods in PortletContainerImpl, I modified the static utility method PortletContextManager.getPortletContext().
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff, P488-trunk-Rev670645.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615136#action_12615136 ]
cdoremus edited comment on PLUTO-488 at 7/20/08 6:30 PM:
--------------------------------------------------------------
Applied P488-trunk-Rev670645.diff patch in rev 678334 and 678336 to pluto-2.0-refactoring branch.
was (Author: cdoremus):
Applied P488-trunk-Rev670645.diff patch in rev 678334 and 678336.
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff, P488-trunk-Rev670645.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-488) When executing
doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the
portlet app fails, a generic NullPointerException is thrown
Posted by "Nikita Dubrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Dubrovsky updated PLUTO-488:
-----------------------------------
Fix Version/s: 1.1.6
Affects Version/s: 1.1.5
> When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-488
> URL: https://issues.apache.org/jira/browse/PLUTO-488
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0, 1.1.5
> Environment: Tomcat 5.5.26
> Reporter: Nikita Dubrovsky
> Priority: Trivial
> Fix For: 2.0.0, 1.1.6
>
> Attachments: P488-1.1.x-Rev656347.diff
>
>
> A very common error when working with JSR-168 portlets for the first time is when the servlet context of the portlet app cannot be accessed by the portal app. This is usually due to an app server misconfiguration (ex: forgetting to set crossContext="true" on Tomcat) or a failed deployment of the portlet app.
> On Pluto 1.1.5, when trying to render a portlet and the servlet context of the portlet app cannot be retrieved, a generic NullPointerException is thrown from DefaultPortletInvokerService.invoke (line 151). It would be much better to throw a PortletContainerException with a detailed message of the problem.
> This is actually already implemented in PortletContainerImpl.getPortletApplicationDescriptor (line 387), but the same logic is not used in the doRender, doAction, doLoad, and doAdmin methods of PortletContainerImpl. This code could be pulled out into a private method on PortletContainerImpl, or it could be placed directly into PortletContextManager.getPortletContext(ServletContext, String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.