1) I would implement PageValidateListener for logic like this. 2) You probably want to use PageRedirectException instead of cycle.activate for changing to the page. 3) Look into callbacks, as well; you may need to implement a custom callback to maintain all of the information you need for the various screens.
Robert Craig Hamilton wrote: > First off, I am using tapestry 3. > > > > I have not been able to solve this in reading the documentation, or the > tapestry in action book, and hope someone can help me out. > > > > There is some context information which needs to be specified before a > set of pages within my app can be shown. I would like to detect that > case within each for the screens, and then redirect to a page I have > for specifying the context info. When the user hits submit, it should > then return back to the page which was attempting to be shown. > > > > For example before ScreenA can be shown, the visit object has to have > certain info filled in. > > > > Within the onFinishLoad method on ScreenA, I detect this, and thought I > could issue a cycle.activate over to my context entry screen. > > > > This didn't work. > > > > Any tips much appreciated. > > > > Thanks > > > > Craig > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
