RE: struts-workflow-extension and DynaValidatorForm

[shirishchandra.sakhare]

Hi Dean,
The struts workflow extension will just work as well with dynaValidatorForms or any 
other type of bean you use as form bean.The only point where it differs from standard 
struts is the ActionMapping.It uses a ActionMapping class of its own.But that also can 
be taken care of.

Just start with it and if you have any questions, there are people in this list(myself 
included) who will be glad to help.

HTH.
Regards,
Shirish.



-Original Message-
From: Dean A. Hoover [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 6:19 PM
To: [EMAIL PROTECTED]
Subject: struts-workflow-extension and DynaValidatorForm


I am interested in using the workflow extension but do
not want to give up using DynaValidatorForm. Is it
possible?

Dean Hoover


-
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]

struts-workflow-extension and DynaValidatorForm

[Dean A. Hoover]

I am interested in using the workflow extension but do
not want to give up using DynaValidatorForm. Is it
possible?
Dean Hoover

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Struts Workflow - Questions ?

[shirishchandra.sakhare]

Also you need not use the session scope for the form.What ever data you want to share 
across pages, you can use workflow container to hold that data...

Have a look at the Demo application and Test Application(available with the  standard 
download ).The test application in fact demonstrates quite a few advanced concepts.It 
has examples of the loop back action as well.

HTH.
Regards,
Shirish




-Original Message-
From: Tommy Holm - TELMORE [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 9:10 AM
To: Struts Users Mailing List
Cc: [EMAIL PROTECTED]
Subject: SV: Struts Workflow - Questions ?


Hi 
I am not sure if I understand your question right, but the way I
understand it is.
You have some action that either can forward to itself (looping) 3 times
( 4 time it should be a workflow violation) or in case everything is ok
forward to another action ?
Well you have a couple of options. You could have a action mapping like
this
 











In your somePossibleLoopingAction you could have a session variable that
holds the count of unsuccessful logins, after the third it could foward
to /someActionThatViolates, this action should of course have some
states that would be violated and then the workflow engine would trigger
a workflow violation where your session forms would be cleaned and you
could eventually make sure that the user is banned or whatever you want.
This should happen in your workflow violation action class. Just make
sure you have a global forward like this !



And then of course the action mapping represented by the
/handleWorkflowLoginViolation.do.


-
makes sure that this workflow is ended 
mailto:[EMAIL PROTECTED] 
Sendt: 2. marts 2004 18:16
Til: [EMAIL PROTECTED]
Emne: Struts Workflow - Questions ?


Hi,

I'm trying to resolve a problem I have by making use of Struts Workflow
- Using this as I need something that will prevent "jump-out" within the
process

The login process of my app has a number of conditions which dictate
which page I send the user to next.

I understand the basic's of the Struts Workflow but am a little confused
when we get to the looping/forwarding aspects

Basically the section of the flow is as follows:

SecurityFilterAuthentication -> Is User Authenticated ?
 If  Y  -> StartWorkflow -> Retrieve User Settings -> Is
3fromN login required ?
   If Y -> Do 3FromN Else ->Record Successful Login ->
...Continue Workflow

The 3FromN section has to allow the user 3 attempts and then do a Lock
Out Action or if successful continue to the Record Successful Login
Action

How do I make those decisions within the workflow ? Do I have to have an
action for every decision node or can I set what the next action should
be in the active one using  return (new ActionForward());

Regards

Joanne Corless



-
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]

SV: Struts Workflow - Questions ?

[Tommy Holm - TELMORE]

Hi 
I am not sure if I understand your question right, but the way I
understand it is.
You have some action that either can forward to itself (looping) 3 times
( 4 time it should be a workflow violation) or in case everything is ok
forward to another action ?
Well you have a couple of options. You could have a action mapping like
this
 











In your somePossibleLoopingAction you could have a session variable that
holds the count of unsuccessful logins, after the third it could foward
to /someActionThatViolates, this action should of course have some
states that would be violated and then the workflow engine would trigger
a workflow violation where your session forms would be cleaned and you
could eventually make sure that the user is banned or whatever you want.
This should happen in your workflow violation action class. Just make
sure you have a global forward like this !



And then of course the action mapping represented by the
/handleWorkflowLoginViolation.do.


-
makes sure that this workflow is ended 
mailto:[EMAIL PROTECTED] 
Sendt: 2. marts 2004 18:16
Til: [EMAIL PROTECTED]
Emne: Struts Workflow - Questions ?


Hi,

I'm trying to resolve a problem I have by making use of Struts Workflow
- Using this as I need something that will prevent "jump-out" within the
process

The login process of my app has a number of conditions which dictate
which page I send the user to next.

I understand the basic's of the Struts Workflow but am a little confused
when we get to the looping/forwarding aspects

Basically the section of the flow is as follows:

SecurityFilterAuthentication -> Is User Authenticated ?
 If  Y  -> StartWorkflow -> Retrieve User Settings -> Is
3fromN login required ?
   If Y -> Do 3FromN Else ->Record Successful Login ->
...Continue Workflow

The 3FromN section has to allow the user 3 attempts and then do a Lock
Out Action or if successful continue to the Record Successful Login
Action

How do I make those decisions within the workflow ? Do I have to have an
action for every decision node or can I set what the next action should
be in the active one using  return (new ActionForward());

Regards

Joanne Corless



-
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]

Struts Workflow - Questions ?

[Joanne L Corless]

Hi,

I'm trying to resolve a problem I have by making use of Struts Workflow -
Using this as I need something that will prevent "jump-out" within the
process

The login process of my app has a number of conditions which dictate which
page I send the user to next.

I understand the basic's of the Struts Workflow but am a little confused
when we get to the looping/forwarding aspects

Basically the section of the flow is as follows:

SecurityFilterAuthentication -> Is User Authenticated ?
 If  Y  -> StartWorkflow -> Retrieve User Settings -> Is 3fromN
login required ?
   If Y -> Do 3FromN Else ->Record Successful Login ->
...Continue Workflow

The 3FromN section has to allow the user 3 attempts and then do a Lock Out
Action or if successful continue to the Record Successful Login Action

How do I make those decisions within the workflow ? Do I have to have an
action for every decision node or can I set what the next action should be
in the active one using  return (new ActionForward());

Regards

Joanne Corless



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Struts Workflow

[shirishchandra.sakhare]

Hi,
I don't think building a real workflow would be that simple.I mean the workflow must 
be built in the framework, the actions being just configured to use it.

And why reinvent the wheel when there is already a solution :-))

Have a look at http://www.livinglogic.de/Struts/

We used it in our project and found that it satisfies most of the requirements.
I am not sure what exactly is your requirement.But the above mentioned extension 
satisfies all workflow requirements.And I am in the process of refactoring it so that 
it provides more extension points for customization.

1.It provides workflow scope.So if you define a group of actions belonging to a 
workflow, they have their own workflow scope.The objects in this scope are available 
only for the duration of the workflow scope.If user jumps out of workflow,the workflow 
scope is cleared.
2.You can define modal dialogue box like screens, where user can be forced to complete 
a workflow/cancel it explicitly before he can jump workflow.

And the best part is,you do not need any code change.All of this is taken care by the 
workflow extension.You only have to configure your action mappings to use workflow.

Have a look at the demo application on the web site.
Also the test application is another replace where you can see how the extension can 
be used in a real world application.

I am in the process of transferring this application to sourceforge.Just transferred 
all source code to sourceforge cvs yesterday :-)).

Have  a look at the extension and let me know if you still have any questions.

HTH.
Regards,
Shirish.



-Original Message-
From: Hookom, Jacob [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 7:58 PM
To: Struts Users Mailing List
Subject: RE: Struts Workflow


No matter what, I would recommend turning off caching on the struts
controller, otherwise you will get anomalies with the back button and
workflows.  Do this early in your development and testing with QA.

-Original Message-
From: Michael McGrady [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 26, 2004 12:42 PM
To: Struts Users Mailing List
Subject: Re: Struts Workflow

My suggestion is to build your own.  This is fairly simple stuff that must 
be wedded to your own way of coding your site or application that will fit 
your business requirements.  Make it general for use in other 
places.  Create, for example, you own do/undo/redo to work with but 
independent of the workflow.  Also create some token application or use the 
one that comes with struts.

At 10:08 AM 2/26/2004, you wrote:
>Does anyone have any great ideas on creating customizable workflows in
Struts?
>
>__
>Do you Yahoo!?
>Get better spam protection with Yahoo! Mail.
>http://antispam.yahoo.com/tools
>
>-
>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]

Struts Workflow

[Mike Duffy]

Does anyone have any great ideas on creating customizable workflows in Struts?

__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts Workflow

[Geeta Ramani]

Mike, search this list's archives. This was discussed a few days ago..

Regards,
Geeta

Mike Duffy wrote:

> Does anyone have any great ideas on creating customizable workflows in Struts?
>
> __
> Do you Yahoo!?
> Get better spam protection with Yahoo! Mail.
> http://antispam.yahoo.com/tools
>
> -
> 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]

Re: Struts Workflow

[Alvaro Martinez]

You can visit this web:
http://www.livinglogic.de/Struts/

Alvaro

- Original Message - 
From: "Mike Duffy" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, February 26, 2004 7:08 PM
Subject: Struts Workflow


Does anyone have any great ideas on creating customizable workflows in
Struts?

__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

-
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]

Re: Struts Workflow

[Michael McGrady]

My suggestion is to build your own.  This is fairly simple stuff that must 
be wedded to your own way of coding your site or application that will fit 
your business requirements.  Make it general for use in other 
places.  Create, for example, you own do/undo/redo to work with but 
independent of the workflow.  Also create some token application or use the 
one that comes with struts.

At 10:08 AM 2/26/2004, you wrote:
Does anyone have any great ideas on creating customizable workflows in Struts?

__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
-
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]

RE: Struts Workflow

[Hookom, Jacob]

No matter what, I would recommend turning off caching on the struts
controller, otherwise you will get anomalies with the back button and
workflows.  Do this early in your development and testing with QA.

-Original Message-
From: Michael McGrady [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 26, 2004 12:42 PM
To: Struts Users Mailing List
Subject: Re: Struts Workflow

My suggestion is to build your own.  This is fairly simple stuff that must 
be wedded to your own way of coding your site or application that will fit 
your business requirements.  Make it general for use in other 
places.  Create, for example, you own do/undo/redo to work with but 
independent of the workflow.  Also create some token application or use the 
one that comes with struts.

At 10:08 AM 2/26/2004, you wrote:
>Does anyone have any great ideas on creating customizable workflows in
Struts?
>
>__
>Do you Yahoo!?
>Get better spam protection with Yahoo! Mail.
>http://antispam.yahoo.com/tools
>
>-
>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]

Struts Workflow Extension

[Alvaro Martinez]

I'm working with "The Struts Workflow Extension" and I think I've found a
bug.
In the example "test" I´ve changed a part in the "struts-comfig.xml"

Before:



  






  

  






  


Now:














...

Well, when I execute the example and I do several loops in the state "wf1-2"
then I change to the workflow "wf2" and the var "pathwf1" is not deleted.
When I go back to the workflow "wf1" then its value stays equal.
Anybody could say me why does it do this one?
Thank you


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Technical question about Struts Workflow Extension

[shirishchandra.sakhare]

Hi,
We have just created an account with source forge for the workflow extension project 
and will be transferring the source code etc. to that account  in the next couple of 
days.
So we are just in early stages of code transfer.
 
But regarding your question.
 
As you said,most of the workflow information can be made available for reading 
atleast.And I had came across similar problem and mr.Matthias bauer had replied that 
it was just overlooked.As this extension was developed/modified as and when the 
requirements arose, it does not have all required extension points and public API.
 
So that is the first task I am going to undertake.To see what parts of workflow can be 
made public and where all extension points are possible so that users can customise 
behaviour of the workflow.
 
And I am planning a next release very soon ,But have no definite schedule.But I am 
really looking forward to getting more such ideas /requests so that the next version 
can be designed keeping into view all of this.
And your requirement has just given me the idea for next immediate release.First thing 
I can do is to atleast make all Workflow state available in readOnly mode so that 
existing users can access use this  functionality without breaking any of the workflow 
logic.
 
Any ideas/suggestions are welcome.
 
I am forwarding this mail to struts user list so that others can also contribute to 
this discussion.
 
regards,
Shirish.
 
 
 
-Original Message-
From: Ignacio Cruzado Nuño [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 8:51 AM
To: Sakhare, Shirishchandra
Subject: Technical question about Struts Workflow Extension


Dear Struts Workflow Extension team:
 
I'm Ignacio Cruzado, from Spain, computer programmer who works on Tecsidel SA (a 
programming company) as a computer consultant.
 
Matthias Bauer gave me your email address in order to redirect this technical 
question... I hope to be writing to the right person (I'm sorry if you are not this 
one!).
 
We are using "struts workflow extension" (SWE) in our development, and we would like 
to access the mapping information that SWE clases manage (the dependencies modelled in 
the struts-config.xml file).
 
In your "Workflow scope" web page you only provide information about the Primary 
Workflow and it's state.
I would find very valuable to have methods to access also to the dependencies of the 
actual state: nextState, prevState, isEndWorkflow and so on...
I have been studying the source code of SWE and I have found out that this information 
is managed by the SWE, but not published (most methods and data structure that manage 
the mapping are on the private/protecthed/package scope, instead of the public scope 
(where I would love to found them!).
Why SWE API design doesn't publish that information? Is there a technical reason for 
that? I'm talking about just readding (get) not establishing or manipulating (set) 
that information.
 
I know that we can change the source code, in order to "open" that information, but 
before doing this I would like to ask you to put much more getter methods in order to 
ask the SWE about the workflow mapping that the developer has established, and get 
more information about the actual state of the workflow.
 
Are you working on that? Is a new release of the SWE scheduled? Is it going to have 
new functionallity in the way I'm asking for?
 
Best regards,
 
  Ignacio
 

Ignacio Cruzado Nuño
Tecsidel S.A.
Parque Tecnológico de Boecillo, Parcela 114
47151 Boecillo (Valladolid)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts workflow problem.Request for enhancement to struts.

[Hubert Rabago]

Here's part of a thread on struts-dev related to your question:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg20449.html

--- [EMAIL PROTECTED] wrote:
> I have used the workflow extension for struts
> (http://www.livinglogic.de/Struts/introduction.html) and found it very useful.
> 
> My question is ..Is there any plan for something similar in next Struts
> release?Is anything similar to a workflow scope which will support wizard like
> flow, being implemented for latest release?I am asking this question because
> before I start working on this extension and think of any further
> enhancements,if something similar is there in standard struts release,I better
> be aware of that.


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Struts workflow problem.Request for enhancement to struts.

[shirishchandra.sakhare]

Hi Guys,
I am not sure if this is the proper place to ask this question or I should be asking 
this in struts developers mailing list.

I have used the workflow extension for struts 
(http://www.livinglogic.de/Struts/introduction.html) and found it very useful.

I think workflow is  a very very common problem we face in any reasonably sized web 
application and most of use end up implementing some application specific solution to 
it.I have been in touch with the Original author of the above mentioned extension(Mr. 
Matthias Bauer) and due to some other commitments,he can no longer devote sufficient 
time to maintain the extension but he has shown his willingness to hand over the 
extension to user community for further maintenance/enhancements .A true open source 
spirit :-))
My question is ..Is there any plan for something similar in next Struts release?Is 
anything similar to a workflow scope which will support wizard like flow, being 
implemented for latest release?I am asking this question because before I start 
working on this extension and think of any further enhancements,if something similar 
is there in standard struts release,I better be aware of that.



For those of you who want to know more about this problem, I have tried to explain the 
scenario.Others can skip this section.


The default scopes provided by Servlet API(Session, request,Page) are not sufficient 
many of the times,a common example being when implementing a wizard like flow.In such 
cases , we need to share data across a number of pages.The common solutions being 
adopted are keeping the data in session(most easy solution, but though very elegant 
for reasons I will explain later),passing around the data as hidden parameters or in 
extreme case, reading the data again.Each of these solutions has drawbacks.
1.Keeping data in session.
The data stays in session till the session expires.There is no guaranteed way of 
removing it from session.because in typical web application, the user has multiple 
exit points from any page, like clicking on any menu item or any other URL so it is 
very difficult to remove data using some generic approach.
2.Passing around data as hidden parameters is reasonable only when data to be passed 
is small.If you have complete tables of data to be passed this way, you unnecessary 
increase the traffic by passing around all this data.
3.Retrieving the data again.
Most crude solution.May not be feasible always & will involve unnecessary trips to 
database.

SO in such cases, if there is an additional scope(WorkflowScope) rpovided by struts, 
then in that case we can just use that without any additional coding.the framework 
will take care of any data cleanup when the user moves out of workflow.The developer 
should just be able to configure a group of actions saying that they are part of a 
Specific WorkFlow.
Also the same workflow processor should be able to take care of other features like 
Not alllowing the user to break the workflow or Warn him before he breaks the 
workflow.This should also be configurable.the current extension I mentioned does all 
this. But it may need to be refactored a bit to provide a bit more extension points 
for customization.




Any suggestions/comments welcome.

regards,
Shirish


Shirish Sakhare
Application Developer
(CEFS PROJECT)
(CEFS) Corporate Employee Financial Services

UBS AG
Stauffacherstrasse 41
P.O. Box, CH-8004 Zürich
Tel: +41-1-235 56 31
Fax: +41-1-235 54 21
Personal Mail Id:[EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Struts Workflow Extension - backwards workflow

[Richard Newton]

I am using the Struts Workflow Extension in a sequence of pages, with one
workflow per page, to prevent users from navigating with the browser buttons,
and this works very well. 
I would however like to have my own back button on some pages so that the user
can go back to a page with attributes etc reset first.
I've tried quite a number of configurations of workflows but have failed to get
it working.
Adding my own back button to the workflow either:
1. re-enables the browser back button on that page, or else
2. causes problems on the page that has been returned to - the submit/next-page
button for that page now generates a previous state violation.
I am not sure whether I am missing something obvious or whether what I am trying
to do is infact logically impossible.
If anyone has implemeted this type of workflow successfully, any advice would be
much appreciated.
Regards, Richard Newton.



This message was sent using IMP, the Internet Messaging Program.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Struts Workflow Extension] Any volunteers for furtherdevelopment and maintenance?

[Matthias Bauer]

Markus,

you are certainly very welcome to ask questions.

--- Matthias

Markus wrote:

Hello Martin,
I've followed the discussion and took a short look over your pages. The
Stuts Workflow Extension 
seems to be an interesting tool and I will take a deeper look in the next
days.
It would be nice if you have time for answering my questions.

Kind regards,

Markus

 

Martin and others who have replied to me off-list:

The Struts Workflow Extension relies on the same ideas of open source 
than the Struts framework does: I had to deal with workflow issues in 
several web applications I developed with Struts about two and a half 
years ago. I noticed that workflow control is needed in almost any web 
application and thus started to develop this extension that focuses on 
solving these issues in a generic and reusable way. I released it as 
open source because of two reasons: The first one is that I (as being a 
consumer of the open source framework Struts) wanted to give something 
back to the community. That's only fair. The second reason to share a 
piece of software is the hope that other people use it, test it and help 
improve it. My company is going on using this software, but there is 
nobody here who feels like being the maintainer of this package, puting 
in time answering questions on this list or privately, doing bugfixes or 
implementing features that are not directly necessary for one of the 
projects implemented here.

I am not asking someone to raise his hand and say: "Ok. I am a really 
good guy, so I will put in a lot of time to maintain a software package 
that is of no use to me."  I am addressing the people that contacted me 
during the last months/years, asking questions about the Struts Workflow 
Extension, reported bugs, donated code and gave all kinds of other 
precious feedback. These people are using this extension and might be 
interested in maintaining it in the future. All I am asking is: Is one 
of these guys willing to be the maintainer of the package, no matter if 
(like up to now) as an extension or a part of the Struts code base (like 
Tiles)?

All the others: Please stop bugging me with: "How much will I get paid 
for?", "What are the conditions?", ... Hey this is open source software. 
The same as Struts.

--- Matthias

Martin Gainty wrote:

   

Matthias:
The problem with most of us is that rent isnt free and food isnt free (at
least not in the US)
Assuming this effort isnt a loaded government project and is more
 

'academic'
   

in nature
How much would your company say this effort is worth?
Saludos,
Martin Gainty
001-617-852-7822
- Original Message - 
From: "Marcus Peixoto" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 7:09 AM
Subject: Re: [Struts Workflow Extension] Any volunteers for
furtherdevelopment and maintenance?



 

Matthias,

How much of your spare time have you been spending on it ?
I have some spare time but I don't know if I have enough experience in
Java to handle it.
[]'s
Marcus

Em Seg, 2003-12-15 Ã s 08:41, Matthias Bauer escreveu:
  

   

Hi everybody,

I am looking for someone who would like to take over further
 

development
   

and responsibility for the Struts Workflow Extension.

The reason I am looking for someone volunteering to do that is simple:
 

I
   

will quit my job at the end of this year and will work in a different
area than web application development from next year on. Unfortunately
even though our company heavily uses this extension, nobody here is
willing to sacrifice a considerable amount of spare time to further
develop and maintain it.
As I know from many questions that were directed to me personally,
 

there
   

are quite some people out there using the extension as well. And as I
would certainly like to see it be actively developed in the future, I
 

am
   

hoping to find somebody who is interested to take over responsibility
for this package. If desired I would assist in transferring the code
 

and
   

documentation to Sourceforge. So anybody who is interested, please
contact me through the mailing list.
Cheers,

--- Matthias



-
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]

Re: [Struts Workflow Extension] Any volunteers for furtherdevelopment and maintenance?

[Markus]

Hello Martin,
I've followed the discussion and took a short look over your pages. The
Stuts Workflow Extension 
seems to be an interesting tool and I will take a deeper look in the next
days.
It would be nice if you have time for answering my questions.


Kind regards,

Markus

> Martin and others who have replied to me off-list:
> 
> The Struts Workflow Extension relies on the same ideas of open source 
> than the Struts framework does: I had to deal with workflow issues in 
> several web applications I developed with Struts about two and a half 
> years ago. I noticed that workflow control is needed in almost any web 
> application and thus started to develop this extension that focuses on 
> solving these issues in a generic and reusable way. I released it as 
> open source because of two reasons: The first one is that I (as being a 
> consumer of the open source framework Struts) wanted to give something 
> back to the community. That's only fair. The second reason to share a 
> piece of software is the hope that other people use it, test it and help 
> improve it. My company is going on using this software, but there is 
> nobody here who feels like being the maintainer of this package, puting 
> in time answering questions on this list or privately, doing bugfixes or 
> implementing features that are not directly necessary for one of the 
> projects implemented here.
> 
> I am not asking someone to raise his hand and say: "Ok. I am a really 
> good guy, so I will put in a lot of time to maintain a software package 
> that is of no use to me."  I am addressing the people that contacted me 
> during the last months/years, asking questions about the Struts Workflow 
> Extension, reported bugs, donated code and gave all kinds of other 
> precious feedback. These people are using this extension and might be 
> interested in maintaining it in the future. All I am asking is: Is one 
> of these guys willing to be the maintainer of the package, no matter if 
> (like up to now) as an extension or a part of the Struts code base (like 
> Tiles)?
> 
> All the others: Please stop bugging me with: "How much will I get paid 
> for?", "What are the conditions?", ... Hey this is open source software. 
> The same as Struts.
> 
> --- Matthias
> 
> 
> Martin Gainty wrote:
> 
> >Matthias:
> >The problem with most of us is that rent isnt free and food isnt free (at
> >least not in the US)
> >Assuming this effort isnt a loaded government project and is more
> 'academic'
> >in nature
> >How much would your company say this effort is worth?
> >Saludos,
> >Martin Gainty
> >001-617-852-7822
> >- Original Message - 
> >From: "Marcus Peixoto" <[EMAIL PROTECTED]>
> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> >Sent: Monday, December 15, 2003 7:09 AM
> >Subject: Re: [Struts Workflow Extension] Any volunteers for
> >furtherdevelopment and maintenance?
> >
> >
> >  
> >
> >>Matthias,
> >>
> >>How much of your spare time have you been spending on it ?
> >>I have some spare time but I don't know if I have enough experience in
> >>Java to handle it.
> >>[]'s
> >>
> >>Marcus
> >>
> >>Em Seg, 2003-12-15 Ã s 08:41, Matthias Bauer escreveu:
> >>
> >>
> >>>Hi everybody,
> >>>
> >>>I am looking for someone who would like to take over further
> development
> >>>and responsibility for the Struts Workflow Extension.
> >>>
> >>>The reason I am looking for someone volunteering to do that is simple:
> I
> >>>will quit my job at the end of this year and will work in a different
> >>>area than web application development from next year on. Unfortunately
> >>>even though our company heavily uses this extension, nobody here is
> >>>willing to sacrifice a considerable amount of spare time to further
> >>>develop and maintain it.
> >>>
> >>>As I know from many questions that were directed to me personally,
> there
> >>>are quite some people out there using the extension as well. And as I
> >>>would certainly like to see it be actively developed in the future, I
> am
> >>>hoping to find somebody who is interested to take over responsibility
> >>>for this package. If desired I would assist in transferring the code
> and
> >>>documentation to Sourceforge. So anybody who is interested, please
> >>>conta

Re: [Struts Workflow Extension] Any volunteers for furtherdevelopment and maintenance?

[Matthias Bauer]

Martin and others who have replied to me off-list:

The Struts Workflow Extension relies on the same ideas of open source 
than the Struts framework does: I had to deal with workflow issues in 
several web applications I developed with Struts about two and a half 
years ago. I noticed that workflow control is needed in almost any web 
application and thus started to develop this extension that focuses on 
solving these issues in a generic and reusable way. I released it as 
open source because of two reasons: The first one is that I (as being a 
consumer of the open source framework Struts) wanted to give something 
back to the community. That's only fair. The second reason to share a 
piece of software is the hope that other people use it, test it and help 
improve it. My company is going on using this software, but there is 
nobody here who feels like being the maintainer of this package, puting 
in time answering questions on this list or privately, doing bugfixes or 
implementing features that are not directly necessary for one of the 
projects implemented here.

I am not asking someone to raise his hand and say: "Ok. I am a really 
good guy, so I will put in a lot of time to maintain a software package 
that is of no use to me."  I am addressing the people that contacted me 
during the last months/years, asking questions about the Struts Workflow 
Extension, reported bugs, donated code and gave all kinds of other 
precious feedback. These people are using this extension and might be 
interested in maintaining it in the future. All I am asking is: Is one 
of these guys willing to be the maintainer of the package, no matter if 
(like up to now) as an extension or a part of the Struts code base (like 
Tiles)?

All the others: Please stop bugging me with: "How much will I get paid 
for?", "What are the conditions?", ... Hey this is open source software. 
The same as Struts.

--- Matthias

Martin Gainty wrote:

Matthias:
The problem with most of us is that rent isnt free and food isnt free (at
least not in the US)
Assuming this effort isnt a loaded government project and is more 'academic'
in nature
How much would your company say this effort is worth?
Saludos,
Martin Gainty
001-617-852-7822
- Original Message - 
From: "Marcus Peixoto" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 7:09 AM
Subject: Re: [Struts Workflow Extension] Any volunteers for
furtherdevelopment and maintenance?

 

Matthias,

How much of your spare time have you been spending on it ?
I have some spare time but I don't know if I have enough experience in
Java to handle it.
[]'s
Marcus

Em Seg, 2003-12-15 Ãs 08:41, Matthias Bauer escreveu:
   

Hi everybody,

I am looking for someone who would like to take over further development
and responsibility for the Struts Workflow Extension.
The reason I am looking for someone volunteering to do that is simple: I
will quit my job at the end of this year and will work in a different
area than web application development from next year on. Unfortunately
even though our company heavily uses this extension, nobody here is
willing to sacrifice a considerable amount of spare time to further
develop and maintain it.
As I know from many questions that were directed to me personally, there
are quite some people out there using the extension as well. And as I
would certainly like to see it be actively developed in the future, I am
hoping to find somebody who is interested to take over responsibility
for this package. If desired I would assist in transferring the code and
documentation to Sourceforge. So anybody who is interested, please
contact me through the mailing list.
Cheers,

--- Matthias



-
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]

Re: [Struts Workflow Extension] Any volunteers for furtherdevelopment and maintenance?

[Martin Gainty]

Matthias:
The problem with most of us is that rent isnt free and food isnt free (at
least not in the US)
Assuming this effort isnt a loaded government project and is more 'academic'
in nature
How much would your company say this effort is worth?
Saludos,
Martin Gainty
001-617-852-7822
- Original Message - 
From: "Marcus Peixoto" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 7:09 AM
Subject: Re: [Struts Workflow Extension] Any volunteers for
furtherdevelopment and maintenance?


> Matthias,
>
> How much of your spare time have you been spending on it ?
> I have some spare time but I don't know if I have enough experience in
> Java to handle it.
> []'s
>
> Marcus
>
> Em Seg, 2003-12-15 Ãs 08:41, Matthias Bauer escreveu:
> > Hi everybody,
> >
> > I am looking for someone who would like to take over further development
> > and responsibility for the Struts Workflow Extension.
> >
> > The reason I am looking for someone volunteering to do that is simple: I
> > will quit my job at the end of this year and will work in a different
> > area than web application development from next year on. Unfortunately
> > even though our company heavily uses this extension, nobody here is
> > willing to sacrifice a considerable amount of spare time to further
> > develop and maintain it.
> >
> > As I know from many questions that were directed to me personally, there
> > are quite some people out there using the extension as well. And as I
> > would certainly like to see it be actively developed in the future, I am
> > hoping to find somebody who is interested to take over responsibility
> > for this package. If desired I would assist in transferring the code and
> > documentation to Sourceforge. So anybody who is interested, please
> > contact me through the mailing list.
> >
> > Cheers,
> >
> > --- Matthias
> >
> >
> >
> > -
> > 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]

Re: [Struts Workflow Extension] Any volunteers for further development and maintenance?

[Marcus Peixoto]

Matthias, 

How much of your spare time have you been spending on it ? 
I have some spare time but I don't know if I have enough experience in
Java to handle it.
[]'s

Marcus

Em Seg, 2003-12-15 Ãs 08:41, Matthias Bauer escreveu:
> Hi everybody,
> 
> I am looking for someone who would like to take over further development 
> and responsibility for the Struts Workflow Extension.
> 
> The reason I am looking for someone volunteering to do that is simple: I 
> will quit my job at the end of this year and will work in a different 
> area than web application development from next year on. Unfortunately 
> even though our company heavily uses this extension, nobody here is 
> willing to sacrifice a considerable amount of spare time to further 
> develop and maintain it.
> 
> As I know from many questions that were directed to me personally, there 
> are quite some people out there using the extension as well. And as I 
> would certainly like to see it be actively developed in the future, I am 
> hoping to find somebody who is interested to take over responsibility 
> for this package. If desired I would assist in transferring the code and 
> documentation to Sourceforge. So anybody who is interested, please 
> contact me through the mailing list.
> 
> Cheers,
> 
> --- Matthias
> 
> 
> 
> -
> 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]

[Struts Workflow Extension] Any volunteers for further development and maintenance?

[Matthias Bauer]

Hi everybody,

I am looking for someone who would like to take over further development 
and responsibility for the Struts Workflow Extension.

The reason I am looking for someone volunteering to do that is simple: I 
will quit my job at the end of this year and will work in a different 
area than web application development from next year on. Unfortunately 
even though our company heavily uses this extension, nobody here is 
willing to sacrifice a considerable amount of spare time to further 
develop and maintain it.

As I know from many questions that were directed to me personally, there 
are quite some people out there using the extension as well. And as I 
would certainly like to see it be actively developed in the future, I am 
hoping to find somebody who is interested to take over responsibility 
for this package. If desired I would assist in transferring the code and 
documentation to Sourceforge. So anybody who is interested, please 
contact me through the mailing list.

Cheers,

--- Matthias



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Struts Workflow] - The workflow definition should allow for dynamic navigation

[Matthias Bauer]

First of all my apologies for the late response to your mails you also 
sent to me personally, but I was on vacation and did not check my 
E-Mails for quite a while.

I feel that the workflow definition, beside of violation detection,
should allow for dynamic navigation.
The framework should provide "tools" to help building apps that's
follows de right workflow. I think of a preventive approach instead of
exclusively relating in postmortem violations detection. 
[...]

Up to now this was beyond the scope of the workflow extension. But if 
you are willing to enhance the standard functionality to cover these 
issues, that's fine with me.

I think it is not a good idea to process "newState" and "endWorkflow"
before executing the Action. 

Problem:

The fact is that an Action can fail. If that happens, such anticipated
state transitions and cleanups are undesired.
Drawbacks of the current design:

If an Action mapping includes "newState" or "endWorkflow" then some sort
of "rollback" must be defined to handle Action's failures.
Instead of going directly to a jsp on every failure (as normal) we
should navigate to a "rollback" action mapping where all modified
workflows states are restituted. The challenge here is to know which
such state was!!!
Also, the custom rollback implementation must provide the reactivation
of those workflows prematurely destroyed.
Solution

Struts don't formalize "Action failure" so there is no way for
StrusWorkflow to know if the Action succeeded or not. 

However, we should define one. For example, a property "failureForward".

The user can specify all forwards representing failures (adding
failureForward properties to the Action mapping). 

In Struts, using the resulting forward path we can determine the
forward. 

If no forward can be determined (no forward was used to create the
resulting forward path) or if the resulting forward doesn't represent a
failure then we proceed to perform the specified "newState" and
"endWorkflow.
If the action fails, no "newState" nor "endWorkflow" must be processed.

The WorkflowRequestProcessor/TilesWorkflowRequestProcessor can easily
handle that. 

Unhandled exceptions

The same discussed for Action failures forwards applies for uncatched
exceptions.
If the Action execution is aborted due to an uncatched exception (being
handle by a Struts error handler or whatever) no "newState" nor
"endWorkflow" shouldn't be processed either.
 

I see your point and I certainly have shed some thoughts on this issue 
as well. I decided against introducing a special forward definition or 
an action property for failure cases like you propose. I admit that this 
approach might appear odd at first, but on the other hand it makes the 
mechanism more straightforward: Each time an action is executed, it 
updates the state information. You can simply rely on that fact. If you 
want to rollback the state you can always do that with an appropriate 
action. Maybe you can elaborate more deeply some cases when this 
approach does not work for you.

--- Matthias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts workflow question

[Matthias Bauer]

Tommy Holm - TELMORE wrote:

Hi
I have a problem which best is described as follows. I have a primary
workflow(WF1) that at a certain time branches off to a secondary
workflow. It is left in a state so that progess can be continued at a
later stage. I my new workflow (WF2) I describe that a secondary
workflow exist(WF1) etc. Now the problem, if WF2 fails, a cleanup of WF2
is performed but WF1 is left untouched which is not desireable. I would
like to cleanup WF1 as well, how can you achieve that ?
If a workflow (in your example wf2) is violated, control is passed to a 
(possibly global) forward definition. This definition should execute an 
action that ends and thus cleans up all workflows that might be in 
progress and needs cleanup.

Now my second question, it should be possible for WF2 to depend on a
secondary workflow (WF3), which means that I want to say, only execute
the action belonging to WF2 if either WF1 is active or WF2. That does
not seem to work. Can you not have more than one secondary workflow ? 
And what if only on of the secondary workflows are active, when the
action associated with with WF2 is executed,  will we have a violation
then ?
 

You can define any number of secondary workflow conditions. If you do, 
all these conditions must be met, otherwise a workflow violation will 
occur. If you want to be able to start wf2 in case either wf1 is in 
state x or wf3 is in state y, you would need two different action 
definitions.

Cheers,

--- Matthias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Struts workflow question

[Tommy Holm - TELMORE]

Hi
I have a problem which best is described as follows. I have a primary
workflow(WF1) that at a certain time branches off to a secondary
workflow. It is left in a state so that progess can be continued at a
later stage. I my new workflow (WF2) I describe that a secondary
workflow exist(WF1) etc. Now the problem, if WF2 fails, a cleanup of WF2
is performed but WF1 is left untouched which is not desireable. I would
like to cleanup WF1 as well, how can you achieve that ?

Now my second question, it should be possible for WF2 to depend on a
secondary workflow (WF3), which means that I want to say, only execute
the action belonging to WF2 if either WF1 is active or WF2. That does
not seem to work. Can you not have more than one secondary workflow ? 
And what if only on of the secondary workflows are active, when the
action associated with with WF2 is executed,  will we have a violation
then ?

Thanks for your time
Cheers
Tommy

Tommy Holm, System Udvikler
TELMORE A/S
Carl Gustavsgade 3, 2630 Taastrup
Telefon 70218700, Mobil 22582344
www.telmore.dk 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Workflow] - Processing "newState" and "endWorkflow" before executing the Action

[Pedro Rodriguez]

I think it is not a good idea to process "newState" and "endWorkflow"
before executing the Action. 
 
Problem:
 
The fact is that an Action can fail. If that happens, such anticipated
state transitions and cleanups are undesired.
 
Drawbacks of the current design:
 
If an Action mapping includes "newState" or "endWorkflow" then some sort
of "rollback" must be defined to handle Action's failures.
 
Instead of going directly to a jsp on every failure (as normal) we
should navigate to a "rollback" action mapping where all modified
workflows states are restituted. The challenge here is to know which
such state was!!!
 
Also, the custom rollback implementation must provide the reactivation
of those workflows prematurely destroyed.
 
Solution
 
Struts don't formalize "Action failure" so there is no way for
StrusWorkflow to know if the Action succeeded or not. 
 
However, we should define one. For example, a property "failureForward".

 
The user can specify all forwards representing failures (adding
failureForward properties to the Action mapping). 
 
In Struts, using the resulting forward path we can determine the
forward. 
 
If no forward can be determined (no forward was used to create the
resulting forward path) or if the resulting forward doesn't represent a
failure then we proceed to perform the specified "newState" and
"endWorkflow.
 
If the action fails, no "newState" nor "endWorkflow" must be processed.
 
The WorkflowRequestProcessor/TilesWorkflowRequestProcessor can easily
handle that. 
 
Unhandled exceptions
 
The same discussed for Action failures forwards applies for uncatched
exceptions.
 
If the Action execution is aborted due to an uncatched exception (being
handle by a Struts error handler or whatever) no "newState" nor
"endWorkflow" shouldn't be processed either.
 
Pedro Rodriguez
 
 

[Struts Workflow] - Workflow Router Struts Action

[Pedro Rodriguez]

I implemented a generic Struts’s Action
which allows for Workflow routing in struts-config.

 

This Action receives an _expression_ via its parameter. We use EL (Jakarta
taglib implementation). Variables are
Workflow’s names and their values the corresponding Workflow’s
state. The _expression_ must evaluate to a Boolean. 

 

The only thing to do to implement a “workflow routing” is
to add a mapping to the struts-config where the
_expression_ (parameter) is provided. 

 

All WorkflowRouter uses the same Action: WorkflowRouterAction.

 



    path="/WorkflowRouter"

    type="MY_PACKAGE.WorkflowRouterAction"

    parameter="${myWorkflowLabel=='some_state'}" >

 

    

     />

  

 

Thanks,

 

Pedro Rodriguez

 

 

 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Workflow] - A taglib to expose any current workflow state

[Pedro Rodriguez]

I wrote this taglib (see attachment) to
expose any current workflow state.

 

Its purpose is to allow workflow-driven navigation in a jsp like that:

 

<strutsWorkflow:getWorkflowState id="myWorkflowState" workflow="myWorkflow" />    

  

<c:choose>

  <c:when test="${ myWorkflowState == 'some_state'}">

    -
A specific Action link here - 

  c:when>

    

  <c:otherwise>

    - some other
Action link here --

  c:otherwise>

c:choose>

 

Do you think it is a good idea or require using the Struts Workflow
framework?

 

This is the tld definition:

 

  <tag>

    <name>getWorkflowStatename>

    <tagclass>MY_PACKAGE.GetWorkflowStateTagtagclass>

    <bodycontent>JSPbodycontent>

    <attribute>

    <name>idname>

    <required>truerequired>

    <rtexprvalue>falsertexprvalue>

    attribute>    

    <attribute>

    <name>workflowname>

    <required>truerequired>

    <rtexprvalue>falsertexprvalue>

    attribute>    

    <attribute>

    <name>toScopename>

    <required>falserequired>

    <rtexprvalue>falsertexprvalue>

    attribute>

  tag>    

 

Thanks a lot,

 

Pedro Rodriguez

 

 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Workflow] - The workflow definition should allow for dynamic navigation

[Pedro Rodriguez]

I feel that the workflow definition, beside of violation detection,
should allow for dynamic navigation.
 
The framework should provide "tools" to help building apps that's
follows de right workflow. I think of a preventive approach instead of
exclusively relating in postmortem violations detection. 
 
Somehow providing features to support the following requirements: 
 
1- Allow actions need to be "decided" in the JSP page.
2- Some generic actions need to route to a specific Action based on
"workflow" status.
 
Do you agree?
 
Thanks a lot,
 
Pedro Rodriguez
 
 

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

[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 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 after this action, because the nextState definition is 
> satisfied, if the state does not change.
> 
> Maybe I should update the documentation with a rule like this:
> 
> "Never set a newState definition to the same value as one of the 
> nextState definitions, as this basically leaves the nextState definition 
> effectless."
> 
> Hope that answers your question.
> 
> --- Matthias
> 
> 
> Axel Gross wrote:
> 
> >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 relevant part of struts-config.xml:
> >
> >  > type="com.livinglogic.struts.workflow.test.Wf1St2Action">
> >>value="com.livinglogic.struts.workflow.test.TestAuthentication" />
> >   
> >   
> >   
> >   
> >   
> >   
> > 
> > 
> >  > type="com.livinglogic.struts.workflow.test.Wf1St2Action">
> >>value="com.livinglogic.struts.workflow.test.TestAuthentication" />
> >   
> >   
> >   
> >   
> >   
> > 
> >
> > 
> >>value="com.livinglogic.struts.workflow.test.TestAuthentication" />
> >   
> >   
> >   
> >   
> >   
> > 
> >
> >  >
> >type="com.livinglogic.struts.workflow.AddSessionAttributeCleanupAction"
> > parameter="pathWf1">
> >>value="com.livinglogic.struts.workflow.test.TestAuthentication" />
> >   
> >   
> >   
> > 
> >
> >
> >
> >What I suggest is killing the '2_loop' state:
> >
> >  > type="com.livinglogic.struts.workflow.test.Wf1St2Action">
> >>value="com.livinglogic.struts.workflow.test.TestAuthentication" />
> >   
> >   
> >   
> >   
> >   
> >   
> > 
> >
> >
> >On 2003-10-20 at 17:07:31 +0200, [EMAIL PROTECTED] wrote:
> > 
> >
> >>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 application of the Struts Workflow 
> >>Extension
> >>(v 1.0.3).
> >>I still couldn't grasp though, why for loop in workflow "wf1" there is a
> >>need for 2 actions.
> >>Maybe you could help me finding out:
> >>Wouldn't it be enough to have
> >> prevState=2
> >> nextState=2
> >> nextState=3
> >> forward success -> inHome.jsp
> >>
> >>thanks in advance,
> >>Axel Gross
> >>   
> >>
> >
> >-
> >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]
> 
> 
--  

 http://www.iaeste.at/~kamikaze/signature.html


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 after this action, because the nextState definition is 
satisfied, if the state does not change.

Maybe I should update the documentation with a rule like this:

"Never set a newState definition to the same value as one of the 
nextState definitions, as this basically leaves the nextState definition 
effectless."

Hope that answers your question.

--- Matthias

Axel Gross wrote:

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 relevant part of struts-config.xml:

 
 type="com.livinglogic.struts.workflow.test.Wf1St2Action">
   
value="com.livinglogic.struts.workflow.test.TestAuthentication" />
   
   
   
   
   
   
 
 
 
 type="com.livinglogic.struts.workflow.test.Wf1St2Action">
   
value="com.livinglogic.struts.workflow.test.TestAuthentication" />
   
   
   
   
   
 

 
   
   
   
   
   
   
 
 

type="com.livinglogic.struts.workflow.AddSessionAttributeCleanupAction"
 parameter="pathWf1">
   
   
   
   
 

What I suggest is killing the '2_loop' state:

 
   
   
   
   
   
   
   
 

On 2003-10-20 at 17:07:31 +0200, [EMAIL PROTECTED] wrote:
 

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 application of the Struts Workflow Extension
(v 1.0.3).
I still couldn't grasp though, why for loop in workflow "wf1" there is a
need for 2 actions.
Maybe you could help me finding out:
Wouldn't it be enough to have
 prevState=2
 nextState=2
 nextState=3
 forward success -> inHome.jsp
thanks in advance,
Axel Gross
   

-
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]

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

[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 relevant part of struts-config.xml:

  







  
  
  






  

  






  

  




  



What I suggest is killing the '2_loop' state:

  







  


On 2003-10-20 at 17:07:31 +0200, [EMAIL PROTECTED] wrote:
> 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 application of the Struts Workflow Extension
> (v 1.0.3).
> I still couldn't grasp though, why for loop in workflow "wf1" there is a
> need for 2 actions.
> Maybe you could help me finding out:
>  Wouldn't it be enough to have
>   prevState=2
>   nextState=2
>   nextState=3
>   forward success -> inHome.jsp
> 
> thanks in advance,
> Axel Gross

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 application of the Struts Workflow Extension
(v 1.0.3).
I still couldn't grasp though, why for loop in workflow "wf1" there is a
need for 2 actions.
Maybe you could help me finding out:
 Wouldn't it be enough to have
  prevState=2
  nextState=2
  nextState=3
  forward success -> inHome.jsp

thanks in advance,
Axel Gross

--  

 http://www.iaeste.at/~kamikaze/signature.html


-
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]

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

[Axel Gross]

Hello!

I had a close look to the test application of the Struts Workflow Extension
(v 1.0.3).
I still couldn't grasp though, why for loop in workflow "wf1" there is a
need for 2 actions.
Maybe you could help me finding out:
 Wouldn't it be enough to have
  prevState=2
  nextState=2
  nextState=3
  forward success -> inHome.jsp

thanks in advance,
Axel Gross

--  

 http://www.iaeste.at/~kamikaze/signature.html


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SSLExt and Struts Workflow?

[Tim Shadel]

Thanks Matthias,

I'm almost positive, the SSL/non-SSL session tracking is taken care in 
SSLExt of by URL rewriting as necessary.  I'll keep an eye out for that 
as I test out my work.  I'll let you know off-list if I have any questions.

Thanks!

Tim

Matthias Bauer wrote:
Tim,

what you are saying seems pretty reasonable. Even though not having 
looked at SSLExt, I don't expect any more collisions than the action 
mapping type and the request processor. When saying that, I am assuming 
that SSLExt correctly copes with session tracking when switching back 
and forth between SSL actions  and non-SSL actions. This is necessary, 
because the workflow state data is kept in the user's session.

If you have any questions or need some support when implementing the 
integration, feel free to come back to me.

--- Matthias

Tim Shadel wrote:

I know this thread is a couple weeks old, but I just started looking 
into this myself.

Actually, I don't think that they are currently compatible, but not 
because of the RequestProcessor.  Matthias has made it easier to write 
a RequestProcessor that includes others, so that should be possible 
(though I haven't done it).  The problem seems to be that they each 
require a custom ActionMappings class:





I assume that you can't use both.  After looking at the code, it 
appears that it may not be hard to change SSLExt to expect an 
Interface instead of a class in most areas that the SecureActionConfig 
is really needed for the config.getSecure() call (WorkflowMapping 
seems to hold more than simple get/set methods).  It seems that the 
changes to SecureActionConfig are most in the checkSsl() and 
computerUrl() methods.  I may be missing something, but it doesn't 
seem like much would break.

Eclpse's "Extract Interface..." refactoring can't do it automatically, 
but gives a quick glance at the areas most affected.  If the SslExt 
code could use an interface, then it would be possible to extend the 
WorkflowMapping, add the needed methods, use the new class in the 
 and then use both SslExt and Struts Workflow together.

Steve and Matthias, do you see any glitches with this approach?  If 
not, I may try to start working at it (isn't that the general rule - 
don't propose something unless you want to volunteer to help? :-D).

Thanks for your great extentions to Struts!

Tim

Matthias Bauer wrote:

If you still want to use the sslext RequestProcessor you should be 
easily able to do that: It is fairly trivial to build an 
SSLExtWorkflowRequestProcessor in just the same way as the 
TilesWorkflowRequestProcesser is built, which is included in the 
Struts Workflow Extension. This is because all the workflow logic is 
extracted into a separate class WorkflowRequestProcessorLogic. If you 
are interested, have a look at the classes WorkflowRequestProcessor, 
TilesWorkflowRequestProcessor, WorkflowRequestProcessorLogic and 
WorkflowRequestProcessorLogicAdapter.

--- Matthias

Steve Ditlinger wrote:

I'll admit to not having used Struts Workflow.  But I don't know of any
reason why sslext should not work, as long as actions are defined in a
struts config file like other struts apps.
If Struts Workflow uses its own RequestProcessor, you would not be 
able to
use the sslext RequestProcessor (without creating your own custom
RequestProcessor).  However, that is OK.  You can use the sslext Plugin
without the sslext RequestProcessor.   Assuming the use of the 
sslext tags,
the sslext RequestProcessor is really only needed as a failsafe for
redirecting to the correct protocol if a URL is improperly 
hand-entered.

HTH,
Steve
- Original Message - From: "Mick Knutson" 
<[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Tuesday, September 23, 2003 2:54 PM
Subject: SSLExt and Struts Workflow?

 

Does SSLExt and Struts Workflow work together?

---
Thanks
Mick Knutson
http://www.baselogic.com
---
-
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]

Re: SSLExt and Struts Workflow?

[Matthias Bauer]

Tim,

what you are saying seems pretty reasonable. Even though not having 
looked at SSLExt, I don't expect any more collisions than the action 
mapping type and the request processor. When saying that, I am assuming 
that SSLExt correctly copes with session tracking when switching back 
and forth between SSL actions  and non-SSL actions. This is necessary, 
because the workflow state data is kept in the user's session.

If you have any questions or need some support when implementing the 
integration, feel free to come back to me.

--- Matthias

Tim Shadel wrote:

I know this thread is a couple weeks old, but I just started looking 
into this myself.

Actually, I don't think that they are currently compatible, but not 
because of the RequestProcessor.  Matthias has made it easier to write 
a RequestProcessor that includes others, so that should be possible 
(though I haven't done it).  The problem seems to be that they each 
require a custom ActionMappings class:





I assume that you can't use both.  After looking at the code, it 
appears that it may not be hard to change SSLExt to expect an 
Interface instead of a class in most areas that the SecureActionConfig 
is really needed for the config.getSecure() call (WorkflowMapping 
seems to hold more than simple get/set methods).  It seems that the 
changes to SecureActionConfig are most in the checkSsl() and 
computerUrl() methods.  I may be missing something, but it doesn't 
seem like much would break.

Eclpse's "Extract Interface..." refactoring can't do it automatically, 
but gives a quick glance at the areas most affected.  If the SslExt 
code could use an interface, then it would be possible to extend the 
WorkflowMapping, add the needed methods, use the new class in the 
 and then use both SslExt and Struts Workflow together.

Steve and Matthias, do you see any glitches with this approach?  If 
not, I may try to start working at it (isn't that the general rule - 
don't propose something unless you want to volunteer to help? :-D).

Thanks for your great extentions to Struts!

Tim

Matthias Bauer wrote:

If you still want to use the sslext RequestProcessor you should be 
easily able to do that: It is fairly trivial to build an 
SSLExtWorkflowRequestProcessor in just the same way as the 
TilesWorkflowRequestProcesser is built, which is included in the 
Struts Workflow Extension. This is because all the workflow logic is 
extracted into a separate class WorkflowRequestProcessorLogic. If you 
are interested, have a look at the classes WorkflowRequestProcessor, 
TilesWorkflowRequestProcessor, WorkflowRequestProcessorLogic and 
WorkflowRequestProcessorLogicAdapter.

--- Matthias

Steve Ditlinger wrote:

I'll admit to not having used Struts Workflow.  But I don't know of any
reason why sslext should not work, as long as actions are defined in a
struts config file like other struts apps.
If Struts Workflow uses its own RequestProcessor, you would not be 
able to
use the sslext RequestProcessor (without creating your own custom
RequestProcessor).  However, that is OK.  You can use the sslext Plugin
without the sslext RequestProcessor.   Assuming the use of the 
sslext tags,
the sslext RequestProcessor is really only needed as a failsafe for
redirecting to the correct protocol if a URL is improperly 
hand-entered.

HTH,
Steve
- Original Message - From: "Mick Knutson" 
<[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Tuesday, September 23, 2003 2:54 PM
Subject: SSLExt and Struts Workflow?

 

Does SSLExt and Struts Workflow work together?

---
Thanks
Mick Knutson
http://www.baselogic.com
---
-
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]

Re: Re: SSLExt and Struts Workflow?

[Steve Ditlinger]

Tim:

Without looking into it too deeply (and without knowing anything about
Workflow), I can say the easiest thing from the sslext side is to redefine
SecureActionConfig to extend WorkflowMapping, just as you say.  If you have
problems, I can look at it more.

Steve


> 
> From: Tim Shadel <[EMAIL PROTECTED]>
> Date: 2003/10/16 Thu PM 01:52:22 CDT
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED],   [EMAIL PROTECTED],  
>  [EMAIL PROTECTED]
> Subject: Re: SSLExt and Struts Workflow?
> 
> I know this thread is a couple weeks old, but I just started looking 
> into this myself.
> 
> Actually, I don't think that they are currently compatible, but not 
> because of the RequestProcessor.  Matthias has made it easier to write a 
> RequestProcessor that includes others, so that should be possible 
> (though I haven't done it).  The problem seems to be that they each 
> require a custom ActionMappings class:
> 
> 
> 
> 
> 
> I assume that you can't use both.  After looking at the code, it appears 
> that it may not be hard to change SSLExt to expect an Interface instead 
> of a class in most areas that the SecureActionConfig is really needed 
> for the config.getSecure() call (WorkflowMapping seems to hold more than 
> simple get/set methods).  It seems that the changes to 
> SecureActionConfig are most in the checkSsl() and computerUrl() methods. 
>   I may be missing something, but it doesn't seem like much would break.
> 
> Eclpse's "Extract Interface..." refactoring can't do it automatically, 
> but gives a quick glance at the areas most affected.  If the SslExt code 
> could use an interface, then it would be possible to extend the 
> WorkflowMapping, add the needed methods, use the new class in the 
>  and then use both SslExt and Struts Workflow together.
> 
> Steve and Matthias, do you see any glitches with this approach?  If not, 
> I may try to start working at it (isn't that the general rule - don't 
> propose something unless you want to volunteer to help? :-D).
> 
> Thanks for your great extentions to Struts!
> 
> Tim
> 
> Matthias Bauer wrote:
> > If you 
> > still want to use the sslext RequestProcessor you should be easily able 
> > to do that: It is fairly trivial to build an 
> > SSLExtWorkflowRequestProcessor in just the same way as the 
> > TilesWorkflowRequestProcesser is built, which is included in the Struts 
> > Workflow Extension. This is because all the workflow logic is extracted 
> > into a separate class WorkflowRequestProcessorLogic. If you are 
> > interested, have a look at the classes WorkflowRequestProcessor, 
> > TilesWorkflowRequestProcessor, WorkflowRequestProcessorLogic and 
> > WorkflowRequestProcessorLogicAdapter.
> > 
> > --- Matthias
> > 
> > 
> > Steve Ditlinger wrote:
> > 
> >> I'll admit to not having used Struts Workflow.  But I don't know of any
> >> reason why sslext should not work, as long as actions are defined in a
> >> struts config file like other struts apps.
> >>
> >> If Struts Workflow uses its own RequestProcessor, you would not be 
> >> able to
> >> use the sslext RequestProcessor (without creating your own custom
> >> RequestProcessor).  However, that is OK.  You can use the sslext Plugin
> >> without the sslext RequestProcessor.   Assuming the use of the sslext 
> >> tags,
> >> the sslext RequestProcessor is really only needed as a failsafe for
> >> redirecting to the correct protocol if a URL is improperly hand-entered.
> >>
> >> HTH,
> >> Steve
> >>
> >>
> >> - Original Message - From: "Mick Knutson" 
> >> <[EMAIL PROTECTED]>
> >> To: "struts" <[EMAIL PROTECTED]>
> >> Sent: Tuesday, September 23, 2003 2:54 PM
> >> Subject: SSLExt and Struts Workflow?
> >>
> >>
> >>  
> >>
> >>> Does SSLExt and Struts Workflow work together?
> >>>
> >>> ---
> >>> Thanks
> >>> Mick Knutson
> >>> http://www.baselogic.com
> >>> ---
> >>>
> >>> -
> >>> 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]

Re: SSLExt and Struts Workflow?

[Tim Shadel]

I know this thread is a couple weeks old, but I just started looking 
into this myself.

Actually, I don't think that they are currently compatible, but not 
because of the RequestProcessor.  Matthias has made it easier to write a 
RequestProcessor that includes others, so that should be possible 
(though I haven't done it).  The problem seems to be that they each 
require a custom ActionMappings class:





I assume that you can't use both.  After looking at the code, it appears 
that it may not be hard to change SSLExt to expect an Interface instead 
of a class in most areas that the SecureActionConfig is really needed 
for the config.getSecure() call (WorkflowMapping seems to hold more than 
simple get/set methods).  It seems that the changes to 
SecureActionConfig are most in the checkSsl() and computerUrl() methods. 
 I may be missing something, but it doesn't seem like much would break.

Eclpse's "Extract Interface..." refactoring can't do it automatically, 
but gives a quick glance at the areas most affected.  If the SslExt code 
could use an interface, then it would be possible to extend the 
WorkflowMapping, add the needed methods, use the new class in the 
 and then use both SslExt and Struts Workflow together.

Steve and Matthias, do you see any glitches with this approach?  If not, 
I may try to start working at it (isn't that the general rule - don't 
propose something unless you want to volunteer to help? :-D).

Thanks for your great extentions to Struts!

Tim

Matthias Bauer wrote:
If you 
still want to use the sslext RequestProcessor you should be easily able 
to do that: It is fairly trivial to build an 
SSLExtWorkflowRequestProcessor in just the same way as the 
TilesWorkflowRequestProcesser is built, which is included in the Struts 
Workflow Extension. This is because all the workflow logic is extracted 
into a separate class WorkflowRequestProcessorLogic. If you are 
interested, have a look at the classes WorkflowRequestProcessor, 
TilesWorkflowRequestProcessor, WorkflowRequestProcessorLogic and 
WorkflowRequestProcessorLogicAdapter.

--- Matthias

Steve Ditlinger wrote:

I'll admit to not having used Struts Workflow.  But I don't know of any
reason why sslext should not work, as long as actions are defined in a
struts config file like other struts apps.
If Struts Workflow uses its own RequestProcessor, you would not be 
able to
use the sslext RequestProcessor (without creating your own custom
RequestProcessor).  However, that is OK.  You can use the sslext Plugin
without the sslext RequestProcessor.   Assuming the use of the sslext 
tags,
the sslext RequestProcessor is really only needed as a failsafe for
redirecting to the correct protocol if a URL is improperly hand-entered.

HTH,
Steve
- Original Message - From: "Mick Knutson" 
<[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Tuesday, September 23, 2003 2:54 PM
Subject: SSLExt and Struts Workflow?

 

Does SSLExt and Struts Workflow work together?

---
Thanks
Mick Knutson
http://www.baselogic.com
---
-
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]

Re: [struts workflow extension]workflow problem incase of validation errors.

[Matthias Bauer]

Shirish,

I really like your mails, because you always seem to be answering your 
questions for yourself. :-)

It does not make any difference whether the validation checks are done 
in the form or the action: The workflows' states have already been 
updated before. Thus, you need to point your input mapping to an action 
that can display the jsp page instead of the jsp page itself. With this 
you have two options:

1. Either your OrderReviewAction does not set a nextState itself, but 
does a forward (in case the checks are passed successfully) to an action 
that sets the nextState condition and continues processing

2. or you define an action RedisplayOrderEntryScreen that satisfies the 
nextState that has been set.

I would clearly prefer the first option. This is also the one that is 
chosen in the demo application.

As you seem to have decided to use the Struts Workflow Extension in one 
of your projects, have you already considered to get a training course 
or project related coaching on this extension. We are offering both. 
This is the way how we fund the development of the extension. If you are 
interested, contact me directly at [EMAIL PROTECTED]

Best regards,

--- Matthias

[EMAIL PROTECTED] wrote:

Hi Mattias,
We have run into another problem with the workflow extension.
We are not using the auto validation mechanism of struts(We set validate=false in action mapping.)

Following is the scenario where we run into problem.The relevant workflow action mapping parameters are indicated in brackets.

Order Entry workflow:
1.page 1 :OrderEntryScreen:The action OrderEntryOpenAction will get the relevant data 
required to be shown to create the order and send the user to order entry 
screen.Configuration for OrderEntryOpenAction is((newState = 1,nextState=2).So when 
the user gets the OrderEntry screen, the action OrderEntryOpenAction  has been already 
executed and hence the workflow is in state 1.
2.When the user says ok on OrderEntry screen, OrderReviewAction is called which on success will send user to OrderReviewWcreen.The OrderReviewAction is configured as (prevState=1,newState = 2,nextState=3).

As we are not using struts auto validation mechanism , the data is validated inside the execute method of action and in case of errors, user is sent back to input which is generally the same jsp which got the input.SO in OrderReviewAction, I perform the validations and I get an validation error, so I do  return new ActionForward(mapping.getInput()); inside the action.But here as we are already inside the execute of the OrderReviewAction, the workflow checks have already been done and the workFlow state is already set to 2(Eventhough in this action we received validation exception.)So when I do a forward to input(which directly goes to jsp),I get workFLow exception because the forward to jsp is just a forward to input of action mapping .And this does not have any of the workFlow attributes set.So this can not pass the previous state or next state checks of the workFLowLogic.

So how have you handled this case?Should the validation failure be also pointing to another mapping which will reset the workFLow state to previous state?

Any ideas are most welcome.

Regards,
Shirish
-
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]

RE: [struts workflow extension]workflow problem incase of validation errors.

[shirishchandra.sakhare]

Hi Mattias,
We have run into another problem with the workflow extension.

We are not using the auto validation mechanism of struts(We set validate=false in 
action mapping.)

Following is the scenario where we run into problem.The relevant workflow action 
mapping parameters are indicated in brackets.

Order Entry workflow:
1.page 1 :OrderEntryScreen:The action OrderEntryOpenAction will get the relevant data 
required to be shown to create the order and send the user to order entry 
screen.Configuration for OrderEntryOpenAction is((newState = 1,nextState=2).So when 
the user gets the OrderEntry screen, the action OrderEntryOpenAction  has been already 
executed and hence the workflow is in state 1.

2.When the user says ok on OrderEntry screen, OrderReviewAction is called which on 
success will send user to OrderReviewWcreen.The OrderReviewAction is configured as 
(prevState=1,newState = 2,nextState=3).

As we are not using struts auto validation mechanism , the data is validated inside 
the execute method of action and in case of errors, user is sent back to input which 
is generally the same jsp which got the input.SO in OrderReviewAction, I perform the 
validations and I get an validation error, so I do  return new 
ActionForward(mapping.getInput()); inside the action.But here as we are already inside 
the execute of the OrderReviewAction, the workflow checks have already been done and 
the workFlow state is already set to 2(Eventhough in this action we received 
validation exception.)So when I do a forward to input(which directly goes to jsp),I 
get workFLow exception because the forward to jsp is just a forward to input of action 
mapping .And this does not have any of the workFlow attributes set.So this can not 
pass the previous state or next state checks of the workFLowLogic.

So how have you handled this case?Should the validation failure be also pointing to 
another mapping which will reset the workFLow state to previous state?

Any ideas are most welcome.

Regards,
Shirish

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [struts workflow extension] design question

[Matthias Bauer]

Shirish,

first of all: Thank you. I certainly like to hear that the Struts 
Workflow Extension meets your requirements and you like the approach I 
have taken.

Regarding the general need to distinguish nextState and prevState 
violations: There is an action contained in the package that can easily 
be used to handle exactly the cases you are talking about: 
ForwardNextStateViolationAction. Here is, what it is meant for: Use this 
class in the action that handles workflow violations. It chooses the 
forward "noNextStateViolation", if there was no nextState violation 
encountered (i. e. it must have been a prevState violation). If a 
nextState violation was encountered it forwards to the path that caused 
this workflow violation (this can be an arbitrary action choosen from 
your menu). If you want to put a message in request/session scope when 
this happens, just write a slightly modified action which is pretty 
similar to ForwardNextStateViolationAction that additionally takes care 
of saving the message. Have a look at the action's code: It uses the 
method WorkflowUtils.getNextStateViolationAction that provides the 
required information.

I chose to take this approach for the following two advantages:
1. the number of global forwards stays smaller, as there is only one 
global forward definition per workflow + in many situations you don't 
even care whether it was a prevState or nextState violation
2. if  you need to distinguish whether you are dealing with a prevState 
or nextState violation and can retrieve the action path that caused the 
workflow violation, do whatever you like and forward the user to this 
path he requested

Concerning your other request for extendability: Yes, I will take care 
of that. Even though it is sometimes good to have extendability 
restricted, because people tend to reimplement their own solutions while 
there are already the right mechanisms available. ;-)

Hope this additional info helps.

--- Matthias

[EMAIL PROTECTED] wrote:

Hi Matthias, 
Thanks for the response.

Right now I my requirements are mostly satisfied by the workflow extention.But as 
pointed out in another recent mail, the ability to specify just one workflow violation 
forward per workflow is a bit constraining.Can you not provide atleast 2 workflow 
violation forwards per workflow?
This will allow the user the configure different page forwards in case of previous 
state condition violation and nest state condition violation.Because I have exactly 
same requirements for some of my pages.Following is the scenario.
Order Entry workflow:
1.page 1 :user selects order parameters and presses ok button.
2.page 2 :order review screen.User can review the order details and then say ok or 
cancel.
3.page 3. User gets the  confirmed order details if he says ok.
Now the requirement is as follows.
1.If the user is in the middle of order entry workflow(say page 2:order review screen) 
and from there he leaves the workflow by clicking some link on menu item.In this case 
he should be allowed to leave the workflow but just a proper warning should be 
displayed on the next page (The page he selected from Menu).
2.The user tries to jump directly in the middle of workflow.(By using bookmark or by 
typing the URL of say page 2:order review screen)In this case he should be  thrown 
back to page 1 of workflow(Order entry screen with proper warning.)
Now as you can see, case 1 is next state violation and case 2 is previous state violation and I want to handle those differently.Also as I want to add a warning in those cases, a post processing hook to the workflow request processor/or workflowProcessorLogic   will be very helpful so that I can add such functionality by extending the workflowProcessorLogic or workflow request processor.

Also about extending the WorkFlowLogic class,most of the other classes have package constructors or their methods are package level /private visibility.So if you can also look into this , it will benefit a lot of users like me who want to extend the functionality of the WorkFlow extension.

All said, I must congratulate you on this very well designed extension.Because after some studies, we found that it meets most of our requirements.

Any suggestions about achieving above mentioned functionality without extending the framework will be really useful.

Regards,
Shirish.
-Original Message-
From: Matthias Bauer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 9:47 AM
To: Struts Users Mailing List
Subject: Re: [struts workflow extension] design question
[EMAIL PROTECTED] wrote:

 

Thanks Matthias,

I will have a close look at the demo and test applications.I need some generic way to add the workflow extention to my existing working screens so that the user will be kept informed of the workflow violations and given a choice to leave the workflow or stay in the workflow.So I am looking at some way to write a generic action which will allow the user to terminat

RE: [struts workflow extension] design question

[shirishchandra.sakhare]

Hi Matthias, 
Thanks for the response.

Right now I my requirements are mostly satisfied by the workflow extention.But as 
pointed out in another recent mail, the ability to specify just one workflow violation 
forward per workflow is a bit constraining.Can you not provide atleast 2 workflow 
violation forwards per workflow?
This will allow the user the configure different page forwards in case of previous 
state condition violation and nest state condition violation.Because I have exactly 
same requirements for some of my pages.Following is the scenario.

Order Entry workflow:
1.page 1 :user selects order parameters and presses ok button.
2.page 2 :order review screen.User can review the order details and then say ok or 
cancel.
3.page 3. User gets the  confirmed order details if he says ok.

Now the requirement is as follows.
1.If the user is in the middle of order entry workflow(say page 2:order review screen) 
and from there he leaves the workflow by clicking some link on menu item.In this case 
he should be allowed to leave the workflow but just a proper warning should be 
displayed on the next page (The page he selected from Menu).
2.The user tries to jump directly in the middle of workflow.(By using bookmark or by 
typing the URL of say page 2:order review screen)In this case he should be  thrown 
back to page 1 of workflow(Order entry screen with proper warning.)

Now as you can see, case 1 is next state violation and case 2 is previous state 
violation and I want to handle those differently.Also as I want to add a warning in 
those cases, a post processing hook to the workflow request processor/or 
workflowProcessorLogic   will be very helpful so that I can add such functionality by 
extending the workflowProcessorLogic or workflow request processor.


Also about extending the WorkFlowLogic class,most of the other classes have package 
constructors or their methods are package level /private visibility.So if you can also 
look into this , it will benefit a lot of users like me who want to extend the 
functionality of the WorkFlow extension.

All said, I must congratulate you on this very well designed extension.Because after 
some studies, we found that it meets most of our requirements.


Any suggestions about achieving above mentioned functionality without extending the 
framework will be really useful.


Regards,
Shirish.

-Original Message-
From: Matthias Bauer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 9:47 AM
To: Struts Users Mailing List
Subject: Re: [struts workflow extension] design question


[EMAIL PROTECTED] wrote:

>Thanks Matthias,
>
>I will have a close look at the demo and test applications.I need some generic way to 
>add the workflow extention to my existing working screens so that the user will be 
>kept informed of the workflow violations and given a choice to leave the workflow or 
>stay in the workflow.So I am looking at some way to write a generic action which will 
>allow the user to terminate or continue in the workflow.
>
>Any how, I will first look at the applications included with download bundle.I hope 
>that i will not be required to extend the workFlowProcessorLogic.
>

You really should not. If there is some required functionality missing 
to accomplish this, I am certainly interested in incorporating this. 
Thus, please let me know, if you are not able to meet your reqirements 
with the current version of the extension.

>But I still have my original doubt.Why does the WorkflowRequestProcessorLogic class 
>not have a public constructor?Should it not be extendable?Or it was a design decision 
>due to some reasons.Because I think keeping in line with the struts philosophy, you 
>could give a couple of extension points in your framework.And the way it is designed, 
>I dont see a reason why it will not become a defacto extention for workflow problems.
>  
>

It was just an oversight not to provide a public constructor. Will keep 
this in my todo list and fix it in the next release.

--- Matthias


-
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]

Re: [struts workflow extension] design question

[Matthias Bauer]

[EMAIL PROTECTED] wrote:

Thanks Matthias,

I will have a close look at the demo and test applications.I need some generic way to add the workflow extention to my existing working screens so that the user will be kept informed of the workflow violations and given a choice to leave the workflow or stay in the workflow.So I am looking at some way to write a generic action which will allow the user to terminate or continue in the workflow.

Any how, I will first look at the applications included with download bundle.I hope that i will not be required to extend the workFlowProcessorLogic.

You really should not. If there is some required functionality missing 
to accomplish this, I am certainly interested in incorporating this. 
Thus, please let me know, if you are not able to meet your reqirements 
with the current version of the extension.

But I still have my original doubt.Why does the WorkflowRequestProcessorLogic class not have a public constructor?Should it not be extendable?Or it was a design decision due to some reasons.Because I think keeping in line with the struts philosophy, you could give a couple of extension points in your framework.And the way it is designed, I dont see a reason why it will not become a defacto extention for workflow problems.
 

It was just an oversight not to provide a public constructor. Will keep 
this in my todo list and fix it in the next release.

--- Matthias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [struts workflow extension] design question

[shirishchandra.sakhare]

Thanks Matthias,

I will have a close look at the demo and test applications.I need some generic way to 
add the workflow extention to my existing working screens so that the user will be 
kept informed of the workflow violations and given a choice to leave the workflow or 
stay in the workflow.So I am looking at some way to write a generic action which will 
allow the user to terminate or continue in the workflow.

Any how, I will first look at the applications included with download bundle.I hope 
that i will not be required to extend the workFlowProcessorLogic.

But I still have my original doubt.Why does the WorkflowRequestProcessorLogic class 
not have a public constructor?Should it not be extendable?Or it was a design decision 
due to some reasons.Because I think keeping in line with the struts philosophy, you 
could give a couple of extension points in your framework.And the way it is designed, 
I dont see a reason why it will not become a defacto extention for workflow problems.

Any thoughts/ideas from other existing users of this extension.

Regards,
Shirish.

-Original Message-
From: Matthias Bauer [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 5:26 PM
To: Struts Users Mailing List
Subject: Re: [struts workflow extension] design question


Shirish,

why do you want to change the workflow extension for doing this? Maybe 
you want to have a look at the demo application. If I am getting you 
right, I suppose I am doing exactly what you want to do: Just let the 
action that handles the workflow violation put the application specific 
warning in the session. With this mechanism you cannot only make this 
warning application specific but even specific to the workflow that is 
violated.

--- Matthias

[EMAIL PROTECTED] wrote:

>Hi ,
>I need to extend the functionality of struts workflow extension provided by Mr. 
>Matthias Bauer( http://www.livinglogic.de/Struts/index.html ).
>
>I want to add some Warning messages when the workflow exception occurs.For the same, 
>I need to Extend the WorkflowRequestProcessorLogic class and override the 
>processCheckWorkflows method so that the ApplicationSpecific Warning can be added in 
>the session.
>
>The method is protected but the class has no public constructor which is preventing 
>me from extending the same.
>
>Can anybody from the committers of the project team me why is this so?Was it a 
>conscious design decision?
>
>TIA.
>
>Shirish
>
>-Original Message-
>From: Adolfo Miguelez [mailto:[EMAIL PROTECTED]
>Sent: Thursday, September 25, 2003 12:08 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Value assignment to html:hidden field...
>
>
>What about this?
>
>
> property="txtBusidate" width="15" size="25" 
>maxlength="25"/>
>
>Adolfo.
>
>
>
>
>  
>
>>From: "Abhijeet Mahalkar" <[EMAIL PROTECTED]>
>>Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>>To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>>Subject: Value assignment to html:hidden field...
>>Date: Thu, 25 Sep 2003 15:09:16 +0530
>>
>>how can we assign the JSP value to the hidden field
>>code is as follows
>>String date = session.getValue("BussinessDate");
>>this date variable i want to assign to following field...
>>>maxlength="25" />
>>
>>will this work ?
>>
>> property="txtBusidate" width="15" size="25" 
>>maxlength="25"/>
>>
>>please suggest
>>abbey
>>
>>
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>_
>Add photos to your messages with MSN 8. Get 2 months FREE*. 
>http://join.msn.com/?page=features/featuredemail
>
>
>-
>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]

Re: [struts workflow extension] design question

[Matthias Bauer]

Shirish,

why do you want to change the workflow extension for doing this? Maybe 
you want to have a look at the demo application. If I am getting you 
right, I suppose I am doing exactly what you want to do: Just let the 
action that handles the workflow violation put the application specific 
warning in the session. With this mechanism you cannot only make this 
warning application specific but even specific to the workflow that is 
violated.

--- Matthias

[EMAIL PROTECTED] wrote:

Hi ,
I need to extend the functionality of struts workflow extension provided by Mr. 
Matthias Bauer( http://www.livinglogic.de/Struts/index.html ).
I want to add some Warning messages when the workflow exception occurs.For the same, I need to Extend the WorkflowRequestProcessorLogic class and override the processCheckWorkflows method so that the ApplicationSpecific Warning can be added in the session.

The method is protected but the class has no public constructor which is preventing me from extending the same.

Can anybody from the committers of the project team me why is this so?Was it a conscious design decision?

TIA.

Shirish

-Original Message-
From: Adolfo Miguelez [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Value assignment to html:hidden field...
What about this?


 property="txtBusidate" width="15" size="25" 
maxlength="25"/>

Adolfo.



 

From: "Abhijeet Mahalkar" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: Value assignment to html:hidden field...
Date: Thu, 25 Sep 2003 15:09:16 +0530
how can we assign the JSP value to the hidden field
code is as follows
String date = session.getValue("BussinessDate");
this date variable i want to assign to following field...
   

will this work ?

 property="txtBusidate" width="15" size="25" 
maxlength="25"/>

please suggest
abbey


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   

_
Add photos to your messages with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

-
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]

[struts workflow extension] design question

[shirishchandra.sakhare]

Hi ,
I need to extend the functionality of struts workflow extension provided by Mr. 
Matthias Bauer( http://www.livinglogic.de/Struts/index.html ).

I want to add some Warning messages when the workflow exception occurs.For the same, I 
need to Extend the WorkflowRequestProcessorLogic class and override the 
processCheckWorkflows method so that the ApplicationSpecific Warning can be added in 
the session.

The method is protected but the class has no public constructor which is preventing me 
from extending the same.

Can anybody from the committers of the project team me why is this so?Was it a 
conscious design decision?

TIA.

Shirish

-Original Message-
From: Adolfo Miguelez [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Value assignment to html:hidden field...


What about this?


 property="txtBusidate" width="15" size="25" 
maxlength="25"/>

Adolfo.




>From: "Abhijeet Mahalkar" <[EMAIL PROTECTED]>
>Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>Subject: Value assignment to html:hidden field...
>Date: Thu, 25 Sep 2003 15:09:16 +0530
>
>how can we assign the JSP value to the hidden field
>code is as follows
>String date = session.getValue("BussinessDate");
>this date variable i want to assign to following field...
> maxlength="25" />
>
>will this work ?
>
> property="txtBusidate" width="15" size="25" 
>maxlength="25"/>
>
>please suggest
>abbey
>
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>

_
Add photos to your messages with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail


-
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]

Re: [struts workflow extension and tiles]Problem with configuring the request processor

[Matthias Bauer]

Glad to hear that,

--- Matthias

[EMAIL PROTECTED] wrote:

Hi Matthias,
It was my fault.The configuration entry I had done to register the controller was 
wrong.
I had written 
com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor
when it should have been .
BTW, I am using struts 1.1 official release.

Thanks for the help.The requestProcessor configuration is working now.

Regards,
Shirish.
-Original Message-
From: Matthias Bauer [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 10:22 AM
To: Struts Users Mailing List
Subject: Re: [struts workflow extension and tiles]Problem with
configuring the request processor 

Shirish,

what Struts version are you using? I certainly tested the 
TilesWorkflowRequestProcessor together with the Tile plugin and it 
worked fine in my setup. Has the Tiles initialization code changed lately?

--- Matthias

[EMAIL PROTECTED] wrote:

 

Hi All,
I am evaluating the struts workflow extension written by Mr. Matthias Bauer( 
http://www.livinglogic.de/Struts/index.html ) And I have found it to be extremely 
useful.But I am facing some problems in configuring it to work with my application.
Right now we are just using tiles, so the struts-config.xml had following entry.






Now with the workflow extenuation, I want to use the Request processor for workflow, so I have added following entry to the struts-config.xml at the very end.



com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor

But when I run the application, What is happening is the request processor being used is still TilesRequestProcessor and not TilesWorkflowRequestProcessor.

The problem seems to be that the tiles plugin changes the ModukleCOnfig with the controller config entry as 
Tiles request Processor.SO somehow my entry in struts-config for controller 
class(com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor),
is being ignored.
As I want to use tiles as well as the workflow extension, I need a way to initialize tiles environment(tell tiles the def files) and also change the RequestProcessor to com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor.

Has anybody used tiles along with this workflow extension?

Any help will be appreciated.

regards,
Shirish
-
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]

RE: [struts workflow extension and tiles]Problem with configuring the request processor

[shirishchandra.sakhare]

Hi Matthias,
It was my fault.The configuration entry I had done to register the controller was 
wrong.
I had written 
com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor
when it should have been .

BTW, I am using struts 1.1 official release.

Thanks for the help.The requestProcessor configuration is working now.

Regards,
Shirish.

-Original Message-
From: Matthias Bauer [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 10:22 AM
To: Struts Users Mailing List
Subject: Re: [struts workflow extension and tiles]Problem with
configuring the request processor 


Shirish,

what Struts version are you using? I certainly tested the 
TilesWorkflowRequestProcessor together with the Tile plugin and it 
worked fine in my setup. Has the Tiles initialization code changed lately?

--- Matthias

[EMAIL PROTECTED] wrote:

>Hi All,
>I am evaluating the struts workflow extension written by Mr. Matthias Bauer( 
>http://www.livinglogic.de/Struts/index.html ) And I have found it to be extremely 
>useful.But I am facing some problems in configuring it to work with my application.
>
>Right now we are just using tiles, so the struts-config.xml had following entry.
>
>
>value="/WEB-INF/config/tiles-defs.xml"/>
>   
>   
> 
>
>
>Now with the workflow extenuation, I want to use the Request processor for workflow, 
>so I have added following entry to the struts-config.xml at the very end.
>
>   
>   
> com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor
>   
>
>But when I run the application, What is happening is the request processor being used 
>is still TilesRequestProcessor and not TilesWorkflowRequestProcessor.
>
>The problem seems to be that the tiles plugin changes the ModukleCOnfig with the 
>controller config entry as Tiles request Processor.SO somehow my entry in 
>struts-config for controller 
>class(com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor),
>is being ignored.
>
>As I want to use tiles as well as the workflow extension, I need a way to initialize 
>tiles environment(tell tiles the def files) and also change the RequestProcessor to 
>com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor.
>
>Has anybody used tiles along with this workflow extension?
>
>Any help will be appreciated.
>
>regards,
>Shirish
>
>
>-
>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]

Re: [struts workflow extension and tiles]Problem with configuring the request processor

[Matthias Bauer]

Shirish,

what Struts version are you using? I certainly tested the 
TilesWorkflowRequestProcessor together with the Tile plugin and it 
worked fine in my setup. Has the Tiles initialization code changed lately?

--- Matthias

[EMAIL PROTECTED] wrote:

Hi All,
I am evaluating the struts workflow extension written by Mr. Matthias Bauer( 
http://www.livinglogic.de/Struts/index.html ) And I have found it to be extremely 
useful.But I am facing some problems in configuring it to work with my application.
Right now we are just using tiles, so the struts-config.xml had following entry.






Now with the workflow extenuation, I want to use the Request processor for workflow, so I have added following entry to the struts-config.xml at the very end.



com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor

But when I run the application, What is happening is the request processor being used is still TilesRequestProcessor and not TilesWorkflowRequestProcessor.

The problem seems to be that the tiles plugin changes the ModukleCOnfig with the controller config entry as 
Tiles request Processor.SO somehow my entry in struts-config for controller 
class(com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor),
is being ignored.
As I want to use tiles as well as the workflow extension, I need a way to initialize tiles environment(tell tiles the def files) and also change the RequestProcessor to com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor.

Has anybody used tiles along with this workflow extension?

Any help will be appreciated.

regards,
Shirish
-
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]

[struts workflow extension]Problem with configuring the request processor

[shirishchandra.sakhare]

Hi All,
I am evaluating the struts workflow extension written by Mr. Matthias Bauer( 
http://www.livinglogic.de/Struts/index.html ) And I have found it to be extremely 
useful.But I am facing some problems in configuring it to work with my application.

Right now we are just using tiles, so the struts-config.xml had following entry.





  


Now with the workflow extenuation, I want to use the Request processor for workflow, 
so I have added following entry to the struts-config.xml at the very end.



com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor


But when I run the application, What is happening is the request processor being used 
is still TilesRequestProcessor and not TilesWorkflowRequestProcessor.

The problem seems to be that the tiles plugin changes the ModukleCOnfig with the 
controller config entry as Tiles request Processor.SO somehow my entry in 
struts-config for controller 
class(com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor),
is being ignored.

As I want to use tiles as well as the workflow extension, I need a way to initialize 
tiles environment(tell tiles the def files) and also change the RequestProcessor to 
com.livinglogic.struts.workflow.TilesWorkflowRequestProcessor.

Has anybody used tiles along with this workflow extension?

Any help will be appreciated.

regards,
Shirish


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SSLExt and Struts Workflow?

[Matthias Bauer]

If you still want to use the sslext RequestProcessor you should be 
easily able to do that: It is fairly trivial to build an 
SSLExtWorkflowRequestProcessor in just the same way as the 
TilesWorkflowRequestProcesser is built, which is included in the Struts 
Workflow Extension. This is because all the workflow logic is extracted 
into a separate class WorkflowRequestProcessorLogic. If you are 
interested, have a look at the classes WorkflowRequestProcessor, 
TilesWorkflowRequestProcessor, WorkflowRequestProcessorLogic and 
WorkflowRequestProcessorLogicAdapter.

--- Matthias

Steve Ditlinger wrote:

I'll admit to not having used Struts Workflow.  But I don't know of any
reason why sslext should not work, as long as actions are defined in a
struts config file like other struts apps.
If Struts Workflow uses its own RequestProcessor, you would not be able to
use the sslext RequestProcessor (without creating your own custom
RequestProcessor).  However, that is OK.  You can use the sslext Plugin
without the sslext RequestProcessor.   Assuming the use of the sslext tags,
the sslext RequestProcessor is really only needed as a failsafe for
redirecting to the correct protocol if a URL is improperly hand-entered.
HTH,
Steve
- Original Message - 
From: "Mick Knutson" <[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Tuesday, September 23, 2003 2:54 PM
Subject: SSLExt and Struts Workflow?

 

Does SSLExt and Struts Workflow work together?

---
Thanks
Mick Knutson
http://www.baselogic.com
---
-
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]

Struts Workflow Docu

[Stephan Wiesner]

Can anybody point me to a good documentation of the Struts Workflow 
extension? The official, so called tutorial, is a little bit short for 
my liking .-(

Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SSLExt and Struts Workflow?

[Steve Ditlinger]

I'll admit to not having used Struts Workflow.  But I don't know of any
reason why sslext should not work, as long as actions are defined in a
struts config file like other struts apps.

 If Struts Workflow uses its own RequestProcessor, you would not be able to
use the sslext RequestProcessor (without creating your own custom
RequestProcessor).  However, that is OK.  You can use the sslext Plugin
without the sslext RequestProcessor.   Assuming the use of the sslext tags,
the sslext RequestProcessor is really only needed as a failsafe for
redirecting to the correct protocol if a URL is improperly hand-entered.

HTH,
Steve


- Original Message - 
From: "Mick Knutson" <[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Tuesday, September 23, 2003 2:54 PM
Subject: SSLExt and Struts Workflow?


> Does SSLExt and Struts Workflow work together?
>
> ---
> Thanks
> Mick Knutson
> http://www.baselogic.com
> ---
>
> -
> 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]

SSLExt and Struts Workflow?

[Mick Knutson]

Does SSLExt and Struts Workflow work together?

---
Thanks
Mick Knutson
http://www.baselogic.com
---

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts-Workflow] Version 1.0.3 released

[Matthias Bauer]

Dear all,

this is to announce, that version 1.0.3 of the Struts Workflow Extension 
has been released.  The package is open source and can be downloaded at: 
http://www.livinglogic.de/Struts/

These are the features that come with the new version:

- Introduced the action AddSessionAttributeCleanupAction
- Reworked the test application
- Improved the demo application
Please send questions and feedback to the Struts user mailing list with 
a subject starting with [Struts-Workflow].

Regards,

--- Matthias



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Struts Workflow] Who is using it?

[Matthias Bauer]

I know of about 30 people having me contacted directly for questions 
since May 15, when version 1.0.0 of the extension came out. All of them 
seemed to be very much willing to use the extension in their projects.

Before Version 1.0.0 there were about 400 downloads per month for about 
half a year (did not track it back further). Since Version 1.0.0 came 
out, the hits and downloads have roughly doubled.

And certainly me and my collegues use the extension in our projects... ;-)

--- Matthias

[EMAIL PROTECTED] wrote:

I have found Matthias Bauer's struts workflow extension and it looks like it
is right what I was looking for. I would like to know, who is actively using
it and whether you found it useful. Anybody willing to share his experience?
Thanks, Pete

 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Workflow] Who is using it?

[pete . barry]

I have found Matthias Bauer's struts workflow extension and it looks like it
is right what I was looking for. I would like to know, who is actively using
it and whether you found it useful. Anybody willing to share his experience?

Thanks, Pete

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Form validation with Struts Workflow

[Matthias Bauer]

Richard,

in the action mapping you can specify the attribute "validate". This 
attribute defaults to true in the ActionMapping class. With the Struts 
Workflow Extension the class ApplicationMapping is used instead of 
ActionMapping. In this class "validate" defaults to false. Thus, if you 
want to switch automatic validation on, you explicitly have to specify  
validate="true" in each action definition.

However, I recommend to do without automatic form validation, when using 
the struts-workflow extension. Here is why:

1. Due to the current implementation of struts and the workflow 
extension, the form validation is done, before authentication and 
workflow has been checked. This is not what you want, because 
authentication and workflow needs to be checked first.

2. You can always call the form.validate() method from the action 
yourself, which I believe is the much better approach anyway, because 
most often you need some additional information from an external data 
source to validate the input (e. g. a password). Obtaining information 
from external data sources should always be done in the action classes, 
not in the form beans.

If I remember correctly, there is no technical reason why automatic form 
validation can not be supported. It should be a minor change to 
eliminate reason (1) in the code. So please let me know, if you really 
need it. I should soon be able to provide a changed version.

--- Matthias


PS: I cc'ed to the struts user list, because conversations like this 
might be relevant to other worklow users, too.



Richard Grossman wrote:

Hi,
 
I'm starting to work using Struts Workflow but I'm confronted to a big 
problem.
It seem that using the workflow the validate method inside ActionForm 
are not called !?!
is there any configuration or else to enabled this ?
 
Thanks for your help
 
Richard Grossman





--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

[Fwd: [ANNOUNCE] Struts Workflow Extension Package 0.9.3]

[Matthias Bauer]

Hi everybody!

I just released Version 0.9.3 of the Struts Workflow Extension Package.

There are no code changes in the package. So why a new version?

* I added instructions for using the test application with Struts 1.1 
 to the file INSTALL.TXT, because some users told me that it was cumbersome
 to only have them on the web pages.
* The package was release with a different license. Due to the fact that I am
 no license expert, I assumed up to now, that the GNU license was appropriate.
 I had to learn that it is pretty restrictive, so I changed it to a BSD-like
 license.

For more information about this package visit 
http://www.livinglogic.de/Struts/

--- Matthias




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Managing a workflow with Struts-workflow.

[Matthias Bauer]

Hi Olivier.

Let me first say this: The workflow extension is not meant to help you 
manage session data and dispatch actions depending on that session data.

Instead it can force the user to follow a sequence of actions that he is 
not allowed to leave. For example think of modal dialogs that are well 
known in desktop gui applications. There you have to click on a button 
the dialog offers before you can do something else in the application. 
One thing that makes web applications more difficult to handle is the 
fact, that you can not rely on a certain request being the next one, 
because the user can alway type in a new url or use the back or reload 
button.

Let's turn to your problem: It I get it right, you do not want to 
"punish" the user (e. g. by displaying an error screen), if he leaves 
this wizard like application. Instead you want to dispatch him depending 
on the data he has already filled in.

What I would recommend to you is this:

- keep an ActionForm in the user's session that collects all the data 
the user has filled in
- in the action form you also keep the  state information which step has 
to be executed next (step1, step2, step3)
- create a wizard-dispatcher that decides where to forward to (depending 
on the state information)


This would look like this:

MainPage.do -> dispatch.do -> 1.jsp -> submitFirstStep.do -> 2.jsp -> 
submitSecondStep.do -> 3.jsp -> submitThirdStep.do -> result.jsp

If someone executes dispatch.do when already having executed 
submitFirstStep.do the state information would be "step2" which results in
-> dispatch.do -> 2.jsp -> ...

You don't have to hard-code the urls into the dispatch action. Instead 
you just need to define forwards for "step1", "step2", ... in the 
struts-config.xml. All the dispatch action does is finding the right 
forward.

I think this is very easy. You don't need an additional framework for 
that...

--- Matthias



ROSSEL Olivier wrote:

I want to have a workflow which is

MainPage.do -> FirstStep.do -> SecondStep.do -> ThirdStep.do -> Result.do ->
MainPage.do
 (1.jsp) (2.jsp)
(3.jsp)

where each step is supposed to fill one part of a big ActionForm.

I think each Step will test if the part of the ActionForm
it handles is already filled (then the current step must be skipped), 
and if so, it forwards to the next action.

Is it the good way to do the job?

I am not sure to see the benefit of using the workflow plug-in.
I declare the workflow in my struts-config.xml, but still have to hard 
code next/previous URLs in my JSPs.

The benefit is of course that the workflow detects if the user
broke the natural chaning by clicking several "Back" in his browser.
But if he did, he could have some reasons, and this may not be an error.

Well, I am sure I misunderstand something, but any help is welcome.

---cut here---


This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

 





--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Managing a workflow with Struts-workflow.

[ROSSEL Olivier]

I want to have a workflow which is

MainPage.do -> FirstStep.do -> SecondStep.do -> ThirdStep.do -> Result.do ->
MainPage.do
  (1.jsp) (2.jsp)
(3.jsp)

where each step is supposed to fill one part of a big ActionForm.

I think each Step will test if the part of the ActionForm
it handles is already filled (then the current step must be skipped), 
and if so, it forwards to the next action.

Is it the good way to do the job?

I am not sure to see the benefit of using the workflow plug-in.
I declare the workflow in my struts-config.xml, but still have to hard 
code next/previous URLs in my JSPs.

The benefit is of course that the workflow detects if the user
broke the natural chaning by clicking several "Back" in his browser.
But if he did, he could have some reasons, and this may not be an error.

Well, I am sure I misunderstand something, but any help is welcome.

---cut here---


This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Problem with struts-workflow distribution (0.9.2)

[ROSSEL Olivier]

It works fine.
You should probably append those Struts1.1 instructions
at the end of the INSTALL.TXT.

I have no easy web access, only the archive.
It was quite annoying. I was almost ready to 
think Workflow was a vaporware :-))

> -Message d'origine-
> De: Matthias Bauer [mailto:[EMAIL PROTECTED]]
> Date: mardi 26 novembre 2002 17:21
> À: ROSSEL Olivier
> Cc: Struts Users Mailing List
> Objet: Re: Problem with struts-workflow distribution (0.9.2)
> 
> 
> Olivier,
> 
> I guess you mean you are trying to build a war of the struts-workflow 
> test application. Please refer to 
> http://www.livinglogic.de/Struts/struts1_1.html for 
> instruction how to 
> modify the test application in order to get it working with 
> struts 1.1.
> 
> According to the stack trace, it looks to me like you have 
> not done the 
> first modification mentioned there: Adding "className" to 
> each action in 
> struts-config.xml.
> 
> When you have done this and still experience problems, let me 
> please know.
> 
> --- Matthias
> 
> 
> PS: I cc'ed to the struts user list, because these 
> conversations might 
> be relevant to other worklow users, too.
> 
> 
> 
> 
> ROSSEL Olivier wrote:
> 
> >I tried to make the war of struts-workflow.
> >It seems that it fails.
> >Because the build.xml forgets to include the commons jar.
> >I miss (at least) common-logging, common-beanutils and 
> common-collections.
> >
> >If I add them manually, it does not complain about missing classes.
> >But it tells me:
> >
> >
> >The server encountered an internal error (Internal Server Error) that
> >prevented it from fulfilling this request.
> >
> >exception
> >
> >javax.servlet.ServletException: 
> org.apache.struts.action.ActionMapping
> > at
> >org.apache.struts.action.RequestProcessor.processException(Re
> questProcessor.
> >java:507)
> > at
> >org.apache.struts.action.RequestProcessor.processActionPerfor
> m(RequestProces
> >sor.java:448)
> > at
> >org.apache.struts.action.RequestProcessor.process(RequestProc
> essor.java:266)
> > at
> >org.apache.struts.action.ActionServlet.process(ActionServlet.
> java:1292)
> > at
> >org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > at
> >org.apache.catalina.core.ApplicationFilterChain.internalDoFil
> ter(Application
> >FilterChain.java:247)
> > at
> >org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl
> icationFilterCh
> >ain.java:193)
> > at
> >org.apache.catalina.core.StandardWrapperValve.invoke(Standard
> WrapperValve.ja
> >va:243)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
> >66)
> > at
> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
> line.java:472)
> > at
> >org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> > at
> >org.apache.catalina.core.StandardContextValve.invoke(Standard
> ContextValve.ja
> >va:190)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
> >66)
> > at
> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
> line.java:472)
> > at
> >org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> > at
> >org.apache.catalina.core.StandardContext.invoke(StandardConte
> xt.java:2347)
> > at
> >org.apache.catalina.core.StandardHostValve.invoke(StandardHos
> tValve.java:180
> >)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
> >66)
> > at
> >org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorD
> ispatcherValve.
> >java:170)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
> >64)
> > at
> >org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor
> tValve.java:170
> >)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
> >64)
> > at
> >org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVal
> ve.java:468)
> > at
> >org.apache.catalina.core.StandardPipeline.invokeNext(Standard
> Pipeline.java:5
&

Re: Problem with struts-workflow distribution (0.9.2)

[Matthias Bauer]

Olivier,

I guess you mean you are trying to build a war of the struts-workflow 
test application. Please refer to 
http://www.livinglogic.de/Struts/struts1_1.html for instruction how to 
modify the test application in order to get it working with struts 1.1.

According to the stack trace, it looks to me like you have not done the 
first modification mentioned there: Adding "className" to each action in 
struts-config.xml.

When you have done this and still experience problems, let me please know.

--- Matthias


PS: I cc'ed to the struts user list, because these conversations might 
be relevant to other worklow users, too.




ROSSEL Olivier wrote:

I tried to make the war of struts-workflow.
It seems that it fails.
Because the build.xml forgets to include the commons jar.
I miss (at least) common-logging, common-beanutils and common-collections.

If I add them manually, it does not complain about missing classes.
But it tells me:


The server encountered an internal error (Internal Server Error) that
prevented it from fulfilling this request.

exception

javax.servlet.ServletException: org.apache.struts.action.ActionMapping
	at
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.
java:507)
	at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:448)
	at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
	at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
	at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:243)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
	at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:190)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
	at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
	at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170
)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
	at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
	at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
	at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1027)
	at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125
)
	at java.lang.Thread.run(Thread.java:484)

root cause

java.lang.ClassCastException: org.apache.struts.action.ActionMapping
	at
com.livinglogic.struts.workflow.GenericAction.perform(GenericAction.java:386
)
	at org.apache.struts.action.Action.execute(Action.java:401)
	at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:446)
	at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
	at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
	at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(Standard

Re: struts workflow

[Matthias Bauer]

Anyone has implementing an workflow engine or workflow application with
struts?



Sorry to answer so late, but I did not have the chance to check the 
mailing list for some time...
Depending how you define "workflow engine" you can have a look at 
http://www.livinglogic.de/Struts/ .

I know two workflow projects

http://www.livinglogic.de/Struts/ integrated with Struts:

and http://jakarta.apache.org/commons/index.html, SandboxComponents, 
Workflow.

No idea if they are the same project or even if there will be any of 
then integrated with the Struts 1.1 release.

I think both have been quite dead right now, is not it? Will Struts 
1.1 release provide any built-in workflow extension? TIA.


Sorry to disagree with you ;-)

The first one is far from being dead. We are using it very successfully 
in our applications. There is a simple reason why there is no boost in 
version numbers: It implements a feature set that is pretty complete for 
our purposes. However, I certainly would not dare to say it is complete ;-)

Regards,

--- Matthias




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[Struts-Workflow] Struts

[Matthias Bauer]

Jordan,

I am CC'ing this mail to the struts user list, cause this might be 
interesting to others, too.

Nobody forces you to use a nextPath attribute. If you do not care which 
action follows next, then you can as well leave the nextState attribute 
away.

But it may as well be, that I am getting something wrong here. If so, 
please help me understand by describing your concrete problem.

--- Matthias



Jordan Thomas wrote:

Hi Matthias,

I am working on a struts app using your workflow extension. Thanks for
that, great stuff. One problem that I do face is that I am unable to
exit a workflow without an error being thrown. I hear you say use the
"nextPath" path attribute. This almost fits but I need to be able to go
anywhere in my application (as long as it is not in the middle of a
workflow). It would be good if we could just specify a "*" value within
the nextPath attribute and then it was easy. Anyway, just a suggestion.

Cheers

Jordan


Jordan Thomas
Fraunhofer-Institut fuer Produktionstechnik und Automatisierung
(FhG-IPA)

Nobelstrasse 12 
D-70569 Stuttgart

Tel.: +49 (0) 711-970-1187
Fax:  +49 (0) 711-970-97-1187
Handi:+49 (0) 150-554-76776

E-mail:   [EMAIL PROTECTED]
Web:  http://www.ipa.fhg.de



 





--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: struts workflow

[Adolfo Miguelez]

Diego,

I know two workflow projects

http://www.livinglogic.de/Struts/ integrated with Struts:

and http://jakarta.apache.org/commons/index.html, SandboxComponents, 
Workflow.

No idea if they are the same project or even if there will be any of then 
integrated with the Struts 1.1 release.

I think both have been quite dead right now, is not it? Will Struts 1.1 
release provide any built-in workflow extension? TIA.

Regards,

Adolfo.








From: "Shay Logan" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: RE: struts workflow
Date: Fri, 15 Nov 2002 14:32:07 -0600

Diego,

At my company we are using struts and weblogic intergrater.  It is going 
pretty good with the development.

Shay

-Original Message-
From: Diego Campodonico [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 15, 2002 9:11 AM
To: [EMAIL PROTECTED]
Subject: struts workflow


Hi,

Anyone has implementing an workflow engine or workflow application with
struts?

I want to do a web application with a workflow engine?
thanks
DIego





--
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]>


_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. 
http://join.msn.com/?page=features/virus


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: struts workflow

[Shay Logan]

Diego,

At my company we are using struts and weblogic intergrater.  It is going pretty good 
with the development.

Shay

-Original Message-
From: Diego Campodonico [mailto:dcampodonico@;netversatile.com]
Sent: Friday, November 15, 2002 9:11 AM
To: [EMAIL PROTECTED]
Subject: struts workflow


Hi,

Anyone has implementing an workflow engine or workflow application with
struts?

I want to do a web application with a workflow engine?
thanks
DIego





--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>




--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>

struts workflow

[Diego Campodonico]

Hi,

Anyone has implementing an workflow engine or workflow application with
struts?

I want to do a web application with a workflow engine?
thanks
DIego





--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[ANNOUNCE] Struts Workflow Extension Package 0.9.2

[Matthias Bauer]

To all struts users!

I just released the Bugfix-Version 0.9.2 of the Struts Workflow 
Extension Package.

The release received the following changes:
* fix for a bug that caused an exception in GenericAction in very 
special configuration situations
* bugfix in the test application's web.xml file, some containers 
stumbled over

For more information about this package visit 
http://www.livinglogic.de/Struts/.

--- Matthias


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>

[ANNOUNCE| Struts Workflow Extension Package V0.9.1

[Matthias Bauer]

To all struts users!

I just released the Bugfix-Version 0.9.1 of the Struts Workflow Extension Package.

It fixes a bug in the test application's web.xml file, some users have stumbled 
over.

Also the web site http://www.livinglogic.de/Struts/ has been updated to describe 
how to use the extension together with Struts 1.1.

--- Matthias


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: [Struts Workflow Extension] Help

[Matthias Bauer]

Yes, specifying multiple prevStates is allowed.

--- Matthias

Amit Harsola wrote:
> Hi Matthias,
> 
> Thanks. It worked. 
> I want to know one more thing. Can there be 2
> prevStates for a single action.
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
> 
> Thanks,
> Amit
> 
> 
> 
> 
> 
> --- Matthias Bauer <[EMAIL PROTECTED]>
> wrote:
> 
>>With your configuration, your are in the following
>>state, after having executed 
>>the action "/main1":
>>
>>- you are allowed to execute any action that leads
>>to the state 2 in workflow "wf2"
>>- you are allowed to execute the action "/main"
>>
>>So, this should admit you to execute the action
>>"/main".
>>
>>However in your definition of the action "/main" you
>>specify that this action 
>>can only be executed if the previous state of "wf1"
>>is "1". You can solve this 
>>issue by rewriting your "/main1" action definition
>>like so:
>>
>> > 
>> > >value="w2" />
>> > 
>> > 
>> > >/>
>> > >value="w1" />
>> > 
>> > >path="createOrderMenuDef"/>
>> >   
>>
>>This makes the state of "wf1" being set to "1" when
>>action "/main1" is executed 
>>and now you can execute "/main"
>>
>>Pls. let me know if it works then,
>>
>>--- Matthias
>>
>>
>>BTW: I would like to have the messages regarding the
>>struts workflow extension 
>>being stored in the struts mailing list archive,
>>therefore I would like to have 
>>our conversation to be sent to the mailing list as
>>well. Nevertheless you should 
>>also set my mail address into the to field, which
>>makes the mail appear in my 
>>inbox instead of being filtered in the struts
>>mailing list folder.
>>
>>
>>
>>
>>Amit Harsola wrote:
>>
>>>Hi,
>>>
>>>I am evaluating Struts workflow extenstion. I have
>>
>>one
>>
>>>problem.
>>>I have three screen index, main and main1 with
>>
>>action
>>
>>>classes as IndexAction, MainAction and
>>
>>Main1Action.
>>
>>>Workflow w1 starts when indexaction is executed
>>
>>and
>>
>>>the current state and next state are 1 and 2 after
>>>this action.
>>>
>>>Control goes to MainAction. Here prev state is
>>
>>defined
>>
>>>as 1 and next Path as Main1Action. After this
>>
>>action
>>
>>>gets executed current state becomes 2 and next
>>
>>state
>>
>>>becomes 3
>>>
>>>Control goes to Main1Action. Now from here If want
>>
>>to
>>
>>>go back to MainAction, how do I do that
>>>
>>>Here r the tags
>>>
>>>
>>>
>>>>
>>value="w1" />
>>
>>>   
>>>
>>>
>>>
>>>
>>>
>>>>
>>value="w1" />
>>
>>>
>>>
>>>
>>>
>>>>
>>/>
>>
>>>
>>>
>>>
>>>
>>>>
>>value="w2" />
>>
>>>
>>>
>>>
>>>>
>>value="w1"
>>
>>>/>
>>>
>>>
>>>TIA,
>>>Amit
>>>
>>>>
>>path="createOrderMenuDef"/>
>>
>>>
>>>
>>>
>>>
>>>__
>>>Do You Yahoo!?
>>>Yahoo! Health - Feel better, live better
>>>http://health.yahoo.com
>>
>>
>>
> 
> 
> __
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: [Struts Workflow Extension] Help

[Amit Harsola]

Hi Matthias,

Thanks. It worked. 
I want to know one more thing. Can there be 2
prevStates for a single action.









   


Thanks,
Amit





--- Matthias Bauer <[EMAIL PROTECTED]>
wrote:
> With your configuration, your are in the following
> state, after having executed 
> the action "/main1":
> 
> - you are allowed to execute any action that leads
> to the state 2 in workflow "wf2"
> - you are allowed to execute the action "/main"
> 
> So, this should admit you to execute the action
> "/main".
> 
> However in your definition of the action "/main" you
> specify that this action 
> can only be executed if the previous state of "wf1"
> is "1". You can solve this 
> issue by rewriting your "/main1" action definition
> like so:
> 
>  > 
>  >  value="w2" />
>  > 
>  > 
>  >  />
>  >  value="w1" />
>  > 
>  >  path="createOrderMenuDef"/>
>  >   
> 
> This makes the state of "wf1" being set to "1" when
> action "/main1" is executed 
> and now you can execute "/main"
> 
> Pls. let me know if it works then,
> 
> --- Matthias
> 
> 
> BTW: I would like to have the messages regarding the
> struts workflow extension 
> being stored in the struts mailing list archive,
> therefore I would like to have 
> our conversation to be sent to the mailing list as
> well. Nevertheless you should 
> also set my mail address into the to field, which
> makes the mail appear in my 
> inbox instead of being filtered in the struts
> mailing list folder.
> 
> 
> 
> 
> Amit Harsola wrote:
> > Hi,
> > 
> > I am evaluating Struts workflow extenstion. I have
> one
> > problem.
> > I have three screen index, main and main1 with
> action
> > classes as IndexAction, MainAction and
> Main1Action.
> > Workflow w1 starts when indexaction is executed
> and
> > the current state and next state are 1 and 2 after
> > this action.
> > 
> > Control goes to MainAction. Here prev state is
> defined
> > as 1 and next Path as Main1Action. After this
> action
> > gets executed current state becomes 2 and next
> state
> > becomes 3
> > 
> > Control goes to Main1Action. Now from here If want
> to
> > go back to MainAction, how do I do that
> > 
> > Here r the tags
> > 
> > 
> > 
> >  value="w1" />
> >   
> > 
> > 
> >
> > 
> > 
> >  value="w1" />
> > 
> > 
> > 
> > 
> >  />
> > 
> > 
> > 
> > 
> >  value="w2" />
> > 
> > 
> > 
> >  value="w1"
> > />
> > 
> > 
> > TIA,
> > Amit
> > 
> >  path="createOrderMenuDef"/>
> >
> > 
> > 
> > 
> > __
> > Do You Yahoo!?
> > Yahoo! Health - Feel better, live better
> > http://health.yahoo.com
> 
> 
> 


__
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Struts Workflow Extension with CactusServletTestCase

[Matthias Bauer]

Chris,

I have not used any Cactus Test Cases with the Workflow Extension, but the 
exception indicates, that the mapping that is passed into the Action's perform 
method is not an instance of com.livinglogic.cms.struts.workflow.ApplicationMapping.

How to resolve this issue depends on what struts version are you using:

In struts 1.0.x the custom ActionMapping (in our case the class
ApplicationMapping) needs to be configured in web.xml:

   mapping
   com.livinglogic.struts.workflow.ApplicationMapping



This does not seem to be supported any longer in Struts 1.1.

Struts 1.1 requires the defintion of the ActionMapping class in each action,
thus allowing you to define different ActionMapping subclasses for each
individual action.

So try the following instead, if you are using a Struts 1.1 version: Include the 
mapping definition in each action in struts-config.xml (I think the attribute is 
className).

Good luck,

   --- Matthias



Homer, Christopher wrote:
> Hi,
> 
> We're currently evaluating the Struts Workflow Extension
> (http://www.livinglogic.de/Struts/index.html) to see whether we can use the
> authentication (and maybe the workflow) mechanisms within our own
> Struts-based application.  Our initial findings have been very positive and
> we have found the authentication to be effective and easy to implement -
> thanks Matthias.
> 
> We are now trying to run a CactusServletTestCase unit test on our prototype
> using the Extension.  We know these unit tests ran successfully prior to
> modifying the code to make use of the Workflow Extension, but unit testing
> after the modifcations produced erroroneous results.
> 
> Has anyone managed to run Cactus Test Cases with the Workflow Extension
> successfully?
> 
> The log of the unit test shows:
> 
> java.lang.ClassCastException: org.apache.struts.action.ActionMapping  at
> com.livinglogic.struts.workflow.GenericAction.perform(GenericAction.java:386
> ) at servletunit.struts.CactusStrutsTestCase.actionPerform(Unknown
> Source)   at
> com.serco.tih.common.tests.TestCactusLoginAction.testSuccessfulLogin(Unknown
> Source)
> 
> Thanks for any help/advice,
> 
> Chris
> 
> For optimum solutions that save you time, visit www.ds-s.com.
> 
> --
> 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]>

Struts Workflow Extension with CactusServletTestCase

[Homer, Christopher]

Hi,

We're currently evaluating the Struts Workflow Extension
(http://www.livinglogic.de/Struts/index.html) to see whether we can use the
authentication (and maybe the workflow) mechanisms within our own
Struts-based application.  Our initial findings have been very positive and
we have found the authentication to be effective and easy to implement -
thanks Matthias.

We are now trying to run a CactusServletTestCase unit test on our prototype
using the Extension.  We know these unit tests ran successfully prior to
modifying the code to make use of the Workflow Extension, but unit testing
after the modifcations produced erroroneous results.

Has anyone managed to run Cactus Test Cases with the Workflow Extension
successfully?

The log of the unit test shows:

java.lang.ClassCastException: org.apache.struts.action.ActionMappingat
com.livinglogic.struts.workflow.GenericAction.perform(GenericAction.java:386
)   at servletunit.struts.CactusStrutsTestCase.actionPerform(Unknown
Source) at
com.serco.tih.common.tests.TestCactusLoginAction.testSuccessfulLogin(Unknown
Source)

Thanks for any help/advice,

Chris

For optimum solutions that save you time, visit www.ds-s.com.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Struts workflow

[Dirk Storck]

Hi,

does someone uses the workflow extension from
http://www.livinglogic.de/Struts/exampleApp.html

Any comments are welcome.
Thanks

Dirk


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Struts Workflow Extension Package V0.9 and Struts 1.1

[Robson Miranda]

Hi...

I also did some testings with this package in Struts 1.1, and got it
working. There was some modifications in that must be done in the example
application so it can work:
In web.xml, the init-parameter "mapping" is not used anymore. Instead, you
must add "className=com.livinglogic.struts.workflow.ApplicationMapping" in
every action in struts-config.xml.
Also, the other "*common.jar" needed in struts 1.1 must be present in the
.war deployed with the sample application.

Robson


- Original Message -
From: "Matthias Bauer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 7:54 AM
Subject: [ANNOUNCE| Struts Workflow Extension Package V0.9


> To all struts users!
>
> It has been quite some time since I first announced the Struts Workflow
> Extension Package. Since then, I have received several requests for an
example
> application and pretty good ideas for further enhancements. Here now is
the
> first official release that includes an example application and most of
the
> suggested enhancements.
>
> I know that there is a proposal and already some work going on in the
Jakarta
> Commons Project for a generic workflow package that is not directly based
on
> Struts, but should be easily integratable. Unfortunately this work is not
> progressing as quickly as some struts user would like to see. Thus, if you
have
> a need (and in each Web-Application you normally have) for workflow
control, try
> this extension and check whether it is appropriate for you.
>
> For more information, the general concepts, documentation and downloading
the
> sources, visit
>
> http://www.livinglogic.de/Struts/
>
> Of course, your feedback is very welcome.
>
> --- Matthias
>
>
> --
> 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]>

[ANNOUNCE| Struts Workflow Extension Package V0.9

[Matthias Bauer]

To all struts users!

It has been quite some time since I first announced the Struts Workflow
Extension Package. Since then, I have received several requests for an example
application and pretty good ideas for further enhancements. Here now is the 
first official release that includes an example application and most of the 
suggested enhancements.

I know that there is a proposal and already some work going on in the Jakarta
Commons Project for a generic workflow package that is not directly based on 
Struts, but should be easily integratable. Unfortunately this work is not 
progressing as quickly as some struts user would like to see. Thus, if you have 
a need (and in each Web-Application you normally have) for workflow control, try 
this extension and check whether it is appropriate for you.

For more information, the general concepts, documentation and downloading the 
sources, visit

http://www.livinglogic.de/Struts/

Of course, your feedback is very welcome.

--- Matthias


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

|ANNOUNCE| Struts Workflow Extensions V0.6

[Matthias Bauer]

Hi all,

my colleague Alexander Lamm and me have implemented an extension to the core 
struts framework which provides rudimentary control flow between actions. It has 
received some considerable rework since the prior version we published and can 
now be configured much more flexible, including multiple parallel workflows.

With its help you can easily (per configuration in struts-config.xml) do the 
following:

- prevent the user from hitting the browser's reload and back buttons which can 
lead to form resubmission and data inconsistencies

- easy definitions of (what we know from non HTML GUIs as) "modal" dialogs in 
struts web applications

- centralized user authentication

- maintenance mode for the whole web application

- and some more...

The file README.TXT which I attached to this mail includes a detailed description.

Ted Husted was so kind to put the code on his Resources Page: 
[http://husted.com/about/struts/resources.htm]
 From there it can be downloaded as a .tgz file that includes all the sources 
and documentation.

One word to the workflow enhancements that are planned to be incorporated into 
Strtus 1.1: Unfortunately I did not have the time to follow the discussions on 
struts-dev as closely as I would have liked to do. So I don't know how much of 
the concepts are similar. The issue here was: We needed some simple workflow 
control for our applications and we needed it now. The planned workflow 
extensions, Craig and others are working on are still far from being finished, 
because they obviously are intended to be much more generic. So we decided to 
implement something that works for us now.

What I want to say is just this: We don't want to compete with the workflow 
extensions some other people are currently working on. If you want, you can just 
view it as an intermediate solution. And yes, I would like to see some of our 
code and concepts be reused for the workflow in Struts 1.1 but don't know if 
this makes sense.

In any case: Your feedback is very welcome.

--- Matthias


The Struts Workflow Extension
=

This extension is meant to provide some rudimentary framework to the
struts application framework.

The code subclasses some struts classes and provides the following
enhancements:

1. Control flow:
   For each action you can specify one or more labeled "workflows" this action
   depends on. In our notion workflows are logical groupings of actions
   following each other in a rather simple, mostly linear or circular way. More
   complicated sequences of actions in an application should be described by
   branching off new workflows at a specific point in a workflow or replacing
   one workflow by another. This means that several workflows are allowed to
   persist or progress in parallel.
   So one of the workflows specified for an action may be defined as "primary",
   i.e. this action belongs to the specified workflow. The others must be
   defined as "secondary", i.e. this action depends on these workflows and can
   influence their progression, but is itself not part of them.
   For each workflow you can specify the following properties:
   a) You can specify a labeled "state" this action leads to in the workflow.
Of course you could also merely store a specific property of the action
itself, e.g. the context-relative URI, to remember the point the
workflow came to after this action. The abstraction we chose is a more
appropriate description of those points though, it helps a lot in
perceiving the progression of a workflow and it opens the faculty, that
two actions lead to the same point in a workflow and that an action
doesn't influence the progresion of the workflow at all.
   b) You can specify labeled states one of which must precede this action in
the workflow. Thus, you can easily prevent someone from hitting the
reload button or using the browser's back button and submit a form for
the second time. The chosen mechanism can replace the token mechanism
provided by struts and brings some further enhancements. A small
example:
An action "displayLogon" displays the logon page of a web application.
It defines the workflow with the label "logon" as its primary workflow
and leads to the state with the label "logonPage" therein. The next
action "logonAction" defines the workflow with the label "logon"
likewise as its primary workflow and the state "logonPage" as its only
allowed preceding state therein. An exception is raised (and causes a
forward to an appropriate error page), if the current state in the
workflow "logon" is not "logonPage" when the action is called. If no
other action can lead to this state, this mean