You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@struts.apache.org by bu...@apache.org on 2006/03/09 03:03:58 UTC

DO NOT REPLY [Bug 38825] - Problem in the sample usecases application

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

http://issues.apache.org/bugzilla/show_bug.cgi?id=38825





------- Additional Comments From craig.mcclanahan@sun.com  2006-03-09 02:03 -------
One thing that can happen with Tomcat in particular is that on a redeploy (or a
shutdown/restart of Tomcat), the session state will be saved and restored.  That
session state will include the beans that Shale uses to track where in the
current dialog you are.  Could this possibly have been the case in your scenario?

Workarounds include:

* Delete the work directory for this app after undeploying

* Include a META-INF/context.xml file in the webapp with the
  following contents:

    <context path="/${context.path}" docBase="${docBase}">
        <manager pathname=""/>
    </context>
 
Leaving this bug report open as a reminder that we should do this by default for
Shale webapps that use dialogs.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org