|
5.9 How to Model a Wizard The J2EE transform recognises special types of pages and events. These should be stereotyped as wizardPages and wizardEvents in a similar way to stereotyping pages and events. You can only have wizardEvents going from one wizardPage to another. Each wizard page has a Back button on it that takes it to the previous page in the wizard and each wizardEvent saves the screen data from the page (assuming it is relevant - search screen data does not get saved). This means that at any point in the wizard, a programmer has available all the data collected in the wizard. When going back to wizard page, if there is stored data available it will be used to fill in the page. As the information is stored by the dataview type backing the page, if information has been collected on one wizardPage, and the same dataview backs another wizardPage further on in the wizard, any data entered in the original page will be populated on reaching the latter one. If you wish to cycle around a wizard, having a link from the end of the wizard to the beginning, you should probably link them with an event, rather than a wizardEvent. This will have the effect of clearing the data from the first pass through the wizard, giving empty initial screens for the next pass. If you want to keep some of the data, but not all, use a wizardEvent and put a business method behind it so that an application programmer can clear the bits of data you don't want.
Link:
Copyright © 2001-2006 New Technology / enterprise Ltd. | |||||||||||||||||||||
