JS2-633 patch seems working OK. If anything else comes up, I will post again. Thank you for your help David.
---Yang >-----Original Message----- >From: David Sean Taylor (JIRA) [mailto:[EMAIL PROTECTED] >Sent: Wednesday, December 20, 2006 4:33 PM >To: [email protected] >Subject: [jira] Commented: (JS2-633) nested layout broken with permission >security enabled > > [ http://issues.apache.org/jira/browse/JS2- >633?page=comments#action_12460058 ] > >David Sean Taylor commented on JS2-633: >--------------------------------------- > >Yang, applied patch to the DBPSML as well, please test and let me know.. > >> nested layout broken with permission security enabled >> ----------------------------------------------------- >> >> Key: JS2-633 >> URL: http://issues.apache.org/jira/browse/JS2-633 >> Project: Jetspeed 2 >> Issue Type: Bug >> Components: Profiler >> Affects Versions: 2.1-dev >> Environment: Tomcat 5 on Windows, potential on IBM WAS >> Reporter: Yang Sie >> Assigned To: David Sean Taylor >> >> with permission security enabled, a page with nested layout generates >null pointer exception under the condition that a portlet in the inner most >nested layout is denied access. >> For example: a page with root layout as oneColumnNoAction, inside this >layout, this are portletA and a TwoColumnNoAction layout. under the >TwoColumnNoAction, portletB at the left cell, and a OneColumn layout at the >right cell. inside the OneColumn layout positioned portletC. if portletC >is forbidden from the current user, while portletA and portletB are OK to >see. Null pointer is thrown. >> In general, if *all* portlets (suppose more than one) under the OneColumn >layout are blocked to the current user, Null Pointer error is thrown. To >make null pointer go away, at least one potlet inside the inner most layout >(OneColumn layout) has to be accessible to user. Another point to note is >that, if the inner most layout (OneColumn layout) has no portlet fragment >at all (means no <fragment type='portlet' .../>. the page is displayed >correctly (i.e. only portletA and portletB apepar on the page, which >*theoritically* should be the same for the display situation, from user >point of view, when portletC is forbidden). Theory is that JS2 treats those >two situations differently somehow. > >-- >This message is automatically generated by JIRA. >- >If you think it was sent incorrectly contact one of the administrators: >http://issues.apache.org/jira/secure/Administrators.jspa >- >For more information on JIRA, see: http://www.atlassian.com/software/jira > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
