[ 
https://issues.apache.org/jira/browse/JS2-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Sean Taylor resolved JS2-633.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1-dev

been running for several months now. 

> nested layout broken with permission security enabled
> -----------------------------------------------------
>
>                 Key: JS2-633
>                 URL: https://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
>             Fix For: 2.1-dev
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to