Bob Schellink <[email protected]>: > Guess it comes down to a preference of constructor vs setter injection. > > I don't see a big problem with exposing the initPage(Page) method on > Context. Perhaps the name initPage might be confused with onInit, so we > should think about whether initPage is the right name. How about > configurePage? We should also give some thought on what will happen if a > user accidentally invokes configurePage after a createPage call. > > Keep in mind that a no-arg Page constructor is still needed if the Page is > to be accessed from the browser, since Click won't know how to construct a > Page which accepts arguments in its constructor. > > Finn, perhaps you can open a JIRA and attach your patch?
Added as CLK-581. It also includes some unit test, but I'm far from certain that the test is done right. Please review and comment. regards, Finn
