Opening up a thread on ALTERNATE SCOPES

[Jonathan Asbell]

Hello all.  We were talking about workflow a few weeks ago and the conversation dissipated.  I am trying to open it up again because I have found a need for more scopes, and a need to implement these new scopes in the next few months.  I am interested specifically in how it can be implemented in Struts. Let me begin with the new scopes.   1) Workflow scope within an application Store values from the first step until the final step and then get rid of the values You could probably use an adaptor, hide implementation from the developer, and store this scope inside the "session" scope Example - within an application store a value Do Activity 1, then do Activity 2, then do Activity 3, then throw out the value     2) Workflow between applications (mentioned by Dan Connelly earlier) Store values from the first step until the final step and then get rid of the values You could probably use an adaptor, hide implementation from the developer, and store this scope inside the "application" scope Example - store a value and do Activity 1 in Application 1, then do Activity 2 in Application 2, then do Activity 3 in Application 3, then throw out the value     3) Sub-Application scope Store values that pertain to a sub-directory within an application You could probably use an adaptor, hide implementation from the developer, and store this scope inside the "session" or "application" scope though I'm not sure which would be more appropriate. Example - Your applcation is a magazine which has 4 different sections, and you want to store values only pertaining to each section.  When you leave the section the value is not visible, and may or may not disappear (depending on what you want to do).