This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am having a conundrum with Stripes and some design issues. I have a Wizard ActionBean that is controlling about 4 different pages that all contain forms. The problem exists with two select fields on the first page:
Only one of those select boxes will ever be used, but later on down the line I will manually (inside the Wizard ActionBean) overwrite the value of the other. So, for example, if the "uploadAndProceed" button is pressed, it will take the value from fileId and do some processing, then later on manually populate the evalFileId value. Alternately if the "proceed" button is pushed, it will take the value in evalFileId, do some processing, then later on manually populate the fileId value.
Because of the Wizard annotation, Stripes is forcing the value of the non-used value throughout the entire process. So even if I manually set it to something else inside the ActionBean, it gets reset by Stripes on the next page, likely due to the hidden field it creates to propagate the value.
So my question is, where can I write that value that it will actually stick, and Stripes won't override it?