> well, I have just shortly skimmed through the article and I > did not see that the issue regarding the back button has > really been solved - what they propose is not to use the back > button but to do the backward navigation server-side....
well, I just looked at it. On "BACK_BUTTON" WFNM sends a request to server, like JSF does by client-side-state-saving. So, if I didn't miss something, it seams to be analog? However, the Struts-Workflow-Ext. I mentioned is available here: http://www.livinglogic.de/Struts/demoApp/index.do you can't click on Screen3 until you have been in Screen1 AND screen2 Regards, Matthias
