Hi, If you download the workflow extension and see the etst app, you will get a better idea.. http://www.livinglogic.de/Struts/exampleApp.html
But as you said, the workflow solution works exactly the way you said...If there is no workflow configured, then the actions will work the normal way. And only if the action mapping has workflow configured, then only workFLow restrictions apply.And also the workflow is highly configurable and you can even have subworkflows or decide where to go in case of workflow exception,like throw back the user to the start of the workflow with a message etc.It can also be used to solve the typical 2 window problem in a web application where user opens child browser window from the main window and after finishing workflow from the parent window, tries to jump at the middle by using the child window. And as i said, it just needs you to use thier requestProcessor and no change of code. We had integrated it in our web application but have taken it out as we are too close to release and the workflow mappings have to carefully analysed. Having said that, i will say that there are some shortcomings which we noticed.But I found it works for all the typical cases of workflow. HTH. regards, Shirish. -----Original Message----- From: Hookom, Jacob [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 7:29 PM To: Struts Users Mailing List Subject: RE: Enhancement Request or Possible Alternative? Vic, I did notice that there is pattern matching now available on the CVS head, but I was wondering if your solution was done with Struts as is, or if you had to make modifications to the Struts Config DTD and/or RequestProcessor? The solution of using a workflow to enforce pathways is not desired since we want to leave that flexibility in most cases and have the business layer resolved with changes of context (finishing/creating). -Jake -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 4:30 AM To: [EMAIL PROTECTED] Subject: RE: Enhancement Request or Possible Alternative? Hi, Did you have a look at the workflow extention for struts?I wil advice you to have alook at the demo application to see if this is what you are looking for. http://www.livinglogic.de/Struts/demoApp.html And also the site has some introductory material...And best of all it is Open Source as well...:-)) It has some similar concept.You can configure actions to make them part of a workflow.And then you can catch when the user leaves the workflow.And then there are various alternatives like you can force them to stay in a workflow or allow them to branch to another workflow. It is highly configurable and does need any code change, just twicking the ActionMappings... regards, Shirish. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Vic Cekvenich Sent: Thursday, December 18, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: Re: Enhancement Request or Possible Alternative? I have a commercial Struts product that includes an event that is generated when a new action is called. I built it so that one can clean up any session stuff when going to another action for large projects. We could work out something VERY reasonable. .V Hookom, Jacob wrote: > We are doing a lot of module switching or multistep workflows (which we > handle fine through session beans) but at the same time, users are allowed > to jump to different pages and we would like to capture a "leave" event when > they aren't within a set of mapping(s). > > I'm wondering if anyone has solved this problem because it would also allow > for constraints on workflows at the action level (if you leave pages X,Y,Z > then fire Action 'CheckSession'). > > -------- > Jacob Hookom > Senior Programmer/Analyst > McKesson Medical-Surgical > Golden Valley, MN --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
