Here is what you are looking for: www.livinglogic.de/Struts/ To get an idea what this extension can do for you, let's look at an example:
The workflow extension can guarantee that the user traverses an application by executing Action A before executing Action B. This way you don't need to check in Action B, if the data that Action A has put into the session is already available, because you can rely on the fact that Action B can only be executed, if Action A has been executed before. I. e. you can design your web application more like a classical GUI application where you have modal dialogs and where you can be perfectly sure, that nobody can send a request you do never expect at this point in time. The baseline is: Your action code becomes far less complex and your application is more robust. Hope this fits your needs. --- Matthias Maurits Blok wrote: > Hi there, > > I'm planning to create some reusable action classes that perform an > autonomous task. Every request will result in the execution of one or > more actions. I'm new to Struts, I've just read some documentation. If I > understand it correctly I have to mention all these actions in the > struts-config file. Is it true that the user can execute any of these > actions from his browser if he knows the right path? If yes, how can I > prevent this? E.g. if a request results in executing 5 actions I only > want to allow the user to start the first action and not any other > actions in the flow, since this breaks the flow. > > Thanks, > Maurits > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
