shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam A. Koch (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SHALE-385) Back button doesn't work between dialog and subdialog
Date Thu, 04 Jan 2007 21:11:16 GMT

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

Adam A. Koch updated SHALE-385:
-------------------------------

    Attachment: bwa.war

> Back button doesn't work between dialog and subdialog
> -----------------------------------------------------
>
>                 Key: SHALE-385
>                 URL: https://issues.apache.org/struts/browse/SHALE-385
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot from 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I get an IllegalStateException when I go to a subdialog, hit the browser back button
and then click on a button for the original dialog.
> Here are the steps to recreate the exception:
> Click on Go to Dialog 1
> Click on Go to Dialog 2
> Click the browser back button
> Click on Cancel
> Expect to go back to the main page, but instead get this exception:
> java.lang.IllegalStateException: Restored stack depth expects 2 but is actually 1
>         at org.apache.shale.dialog.basic.BasicDialogContext.setOpaqueState(BasicDialogContext.java:299)
>         at org.apache.shale.dialog.faces.DialogPhaseListener.restore(DialogPhaseListener.java:322)
>         at org.apache.shale.dialog.faces.DialogPhaseListener.afterRestoreView(DialogPhaseListener.java:189)
>         at org.apache.shale.dialog.faces.DialogPhaseListener.afterPhase(DialogPhaseListener.java:126)
>         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:211)
>         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
>         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
>         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
>         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
>         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
>         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
>         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
>         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
>         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
>         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
>         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message