The following comment has been added to this issue:

     Author: Arthur D'Alessandro
    Created: Mon, 4 Oct 2004 2:27 PM
       Body:
We ended up taking the recomendation of Tomasz Gajewski ([EMAIL PROTECTED])

By maintaining the action events inside the buildConfigurContext then redirecting to 
the action=controls.Restore after we did the config saves from within 
buildConfigurContext.  Although this is not optimal, it did however resolve our 
immediate problems of having to deal with a broken interface (missing navigation and 
delayed portlet title changes)

We simply maintain a submitaction and test this against known good commands;
eg save => saving the configuration->
Changing from Customize mode back to Restored mode, or displaying the customize screen.

After saving, we setTempalte to a self submitting form, which posts back to itself 
(form action='$jslink') with a hidden form param, action=controls.Restore.

This breaks the action class model, and is not the best solution.

We have been unable to resolve outside of this posted work-around.

Is this something that will be fixed in 1.6, or 2.0?
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JS1-520?page=comments#action_53690

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS1-520

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS1-520
    Summary: provides.Customization and update action yields does not return to proper 
view eg. controls.Restore
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Jetspeed
 Components: 
             Customizer
   Versions:
             1.5

   Assignee: 
   Reporter: Arthur D'Alessandro

    Created: Fri, 1 Oct 2004 9:20 AM
    Updated: Mon, 4 Oct 2004 2:27 PM
Environment: JS1.5
Tomcat 5.0.27
Linux|WindowsXP

Description:
When we provide our own customization (buildConfigurcontext), we are presented 
properly with the customization screen, however, handling the update fails to return 
the portlet screen to normal.  We loose the Top navigation until we invoke one of the 
controls.x, eg, maximum and restore.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Reply via email to