Re: [Struts Workflow] Test application - why two actions for loop? [solved]

2003-10-22 Thread Axel Gross
Thanks Mathias! That makes everything clear. I think you should do that documentation update, it's so crucial to workflow security and at least I didn't get that point without asking :)) Dankeschön nochmals! Axel On 2003-10-21 at 09:21:08 +0200, Matthias Bauer wrote: > Axel, > > your suggestion

Re: [Struts Workflow] Test application - why two actions for loop?

2003-10-21 Thread Matthias Bauer
Axel, your suggestion unforunately does not work as you would expect. The action definition you are suggesting defines nextState=2 and newState=2. This means, that after the action has been executed, the wf1 is in state 2. Thus, any action that does not change the state of wf1 can be executed

Re: [Struts Workflow] Test application - why two actions for loop?

2003-10-20 Thread Axel Gross
Well. If you take a look at the struts-config.xml you'll see that there are two actions defined: wf1St2Loop and wf1St2LoopEnd The second is just a forward changing workflow values. I just can't figure out a reason, why there are two instead of one simpler action. for your convenience, original

RE: [Struts Workflow] Test application - why two actions for loop?

2003-10-20 Thread shirishchandra.sakhare
can you elaborate a little? Too less info :-(( -Original Message- From: Axel Gross [mailto:[EMAIL PROTECTED] Sent: Monday, October 20, 2003 5:03 PM To: [EMAIL PROTECTED] Subject: [Struts Workflow] Test application - why two actions for loop? Hello! I had a close look to the test appli