DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8129>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8129

Switching from 3 column to 2 column layout is broken

           Summary: Switching from 3 column to 2 column layout is broken
           Product: Jetspeed
           Version: 1.3a3-dev / CVS
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Customizer
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Switching from a 3 column layout to a 2 column layout in current CVS (and for as
long as I've checked) is broken.  The customizer throws an
ArrayIndexOutOfBoundException internally, which ends up leaving the user with no
portlets displayed until they switch their layout back to a 3-column layout. 
I'm not sure, but I would guess the same thing would happen if a switch from a 2
column to single column layout was made.

After some time under the debugger, I've narrowed the problem down to the method
"protected static List[] buildColumns(Portlets set, int colNum)" in the
org.apache.jetspeed.modules.actions.controllers.MultiColumnControllerAction class.  

The exception is occuring on line 662 of this file due to the fact that the
array of List instances has two entries, but the portlet still wants to be in
the 3rd column (index 2).  It may be that the test on line 594 needs to be 
if (col >= colNum) 
instead of
if (col > colNum)

When I tried this, I was able to get from a 3 column to 2 column layout
successfully, but I was unable to move things back into the 3rd column when
switching back to a 3 column layout.  After that, it appears that my PSML is
completely hosed.  This is obviously beyond my current understanding of all of
this code.

I'd be happy to provide more information as necessary.

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

Reply via email to