[ 
https://issues.apache.org/jira/browse/JS2-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854313#action_12854313
 ] 

Randy Watler commented on JS2-1174:
-----------------------------------

These customizer operations appear to be broken in 2.2.1 trunk as well.

> Change folder name action in the Page/Folder Customizer displays incorrect 
> data after a change operation is completed. 
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1174
>                 URL: https://issues.apache.org/jira/browse/JS2-1174
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Customizer
>    Affects Versions: 2.2.0
>         Environment: Windows XP, jdk1.5.0_16
>            Reporter: Jeff Pierce
>            Assignee: Randy Watler
>            Priority: Minor
>
> Change folder name action in the Page/Folder Customizer does not appear to be 
> working correctly.  It seems the "commits" to my name changes were 1 behind.  
> I made a change, didn't see any differences in the interface.  Then I made 
> another change and saw the change appear from try 1.  Made another change 
> (try 3) and saw the change from try 2 show up.  The PSML files on disk seemed 
> to contain the correct, last changed information, but the interface was not 
> showing the correct information.  It was not until I logged out and restarted 
> my server that the changes displayed in the interface "caught up" with the 
> changes I had made using the interface and what was actually stored in the 
> PSML files.  The physical names on disk never changed as well.  I was not 
> using the database storage for PSML.  This was done using the min installer 
> for Jetspeed 2.2.0. 

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