From: Anjo K. <anj...@t-...> - 2004-04-11 20:19:05
|
Am 10.04.2004 um 18:44 schrieb Ashley Aitken: > I'm wondering, however, how D2W determines the pageConfigurations for > pages subsequent to the one specified by my pageConfiguration. It doesn't. The pages following are either defined by the action buttons, the ERDActionButton or ERDActionBar subclasses in the page. They are open to enhancement, but mostly you define a "xxxConfigurationName" for the given pageConfiguration: pageConfiguration ="QueryMyFoo" => listConfigurationName = "ListMyFoo" > One can actually go quite deep like this, query page -> list page -> > edit page -> edit relationship page -> edit new page .... That's where the ERD2WControllerFactory is supposed to fill in, but it's still holidays, so you should search the archives and read the docs first:) > Somehow the rule engine seems to choose (or allocate) a configuration > eg __edit__Employee or EditEmployee" but the thing is as it is setting > it I can't seem to have more than one configuration for different > contexts. > > For example, if I had QueryEmployee1 and QueryEmployee2 > pageConfigurations, currently they both lead to a list page (that I > can choose a configuration for using nextPageDelegate) but they would > share a common edit page for the Employee. Not what I want. See above. Cheers, Anjo |