Re: AW: Workflow Extention

2002-12-06 Thread Matthias Bauer
: Thursday, 5 December 2002 3:30 PM To: Jordan Thomas Cc: Struts User List Subject: Re: AW: Workflow Extention Jordan, the configuration looks ok to me. Can you please send me the complete log messages. They should look somehow like these (I took them from the example application): 2002-12-05

RE: AW: Workflow Extention

2002-12-05 Thread Jordan Thomas
To: [EMAIL PROTECTED] Cc: 'Struts Users Mailing List' Subject: Re: AW: Workflow Extention Jordan, I think I understand pretty well, what you are trying to do. However according to your configuration you should not be able to execute /registration/2 before having executed /registration/1. Here are some

Re: AW: Workflow Extention

2002-12-05 Thread Matthias Bauer
Jordan, the configuration looks ok to me. Can you please send me the complete log messages. They should look somehow like these (I took them from the example application): 2002-12-05 15:27:52 action: Processing a GET for /beginWf1Transition 2002-12-05 15:27:52 action: Looking for Action

RE: AW: Workflow Extention

2002-12-05 Thread Jordan Thomas
-workflow 17:00:08,292 INFO [Engine] action: Previous state does not match any allowed previous state! -Original Message- From: Matthias Bauer [mailto:[EMAIL PROTECTED]] Sent: Thursday, 5 December 2002 3:30 PM To: Jordan Thomas Cc: Struts User List Subject: Re: AW: Workflow Extention

RE: Workflow Extention

2002-11-27 Thread Jordan Thomas
]] Sent: Tuesday, 26 November 2002 8:36 AM To: Struts Users Mailing List Subject: Re: Workflow Extention Hi Jordan, sorry for the late response... You can not specify a wildcard like * for nextPath - the framework does not support that up to now. I would be happy to integrate it, if you can

Re: Workflow Extention

2002-11-27 Thread Matthias Bauer
8:36 AM To: Struts Users Mailing List Subject: Re: Workflow Extention Hi Jordan, sorry for the late response... You can not specify a wildcard like * for nextPath - the framework does not support that up to now. I would be happy to integrate it, if you can explain a valid use case

AW: Workflow Extention

2002-11-27 Thread Jordan Thomas
. Cheers and thanks for the help Jordan -Ursprüngliche Nachricht- Von: Matthias Bauer [mailto:[EMAIL PROTECTED]] Gesendet: Wednesday, 27 November 2002 1:22 PM An: [EMAIL PROTECTED] Cc: 'Struts Users Mailing List' Betreff: Re: Workflow Extention Jordan, according to the configuration

Re: AW: Workflow Extention

2002-11-27 Thread Matthias Bauer
to solve this one. Cheers and thanks for the help Jordan -Ursprüngliche Nachricht- Von: Matthias Bauer [mailto:[EMAIL PROTECTED]] Gesendet: Wednesday, 27 November 2002 1:22 PM An: [EMAIL PROTECTED] Cc: 'Struts Users Mailing List' Betreff: Re: Workflow Extention Jordan, according

RE: Workflow Extention

2002-11-26 Thread Jordan Thomas
Thanks Matthias, I'll try it out and let you know how it goes. Regards Jordan -Original Message- From: Matthias Bauer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 8:36 AM To: Struts Users Mailing List Subject: Re: Workflow Extention Hi Jordan, sorry for the late

Re: Workflow Extention

2002-11-25 Thread Matthias Bauer
only be executed, if the workflow is in state 1 (i. e. action A has been executed) and action C can only be executed, if the workflow is in state 2 (i. e. action B has been executed). Pls. let me know, if this helps. --- Matthias Jordan Thomas wrote: Hi All, I am using the workflow extention

Workflow Extention

2002-11-21 Thread Jordan Thomas
Hi All, I am using the workflow extention to create my workflows. It seems that when I am in the middle of a workflow, there is no way to allow the user to jump out of the workflow into another area of the application. I have tried specifying a * and a *.do as a nextPath parameter

Workflow Extention

2002-11-21 Thread Jordan Thomas
Hi All, I am using the workflow extention to create my workflows. It seems that when I am in the middle of a workflow, there is no way to allow the user to jump out of the workflow into another area of the application. I have tried specifying a * and a *.do as a nextPath parameter