There really isn't a good reason to remove them even if parameter injection is added. If they have to be removed at least deprecate and remove in v 8.
On Thu, Aug 22, 2013 at 12:26 PM, Martijn Dashorst < [email protected]> wrote: > On Thu, Aug 22, 2013 at 6:24 PM, Ben Tilford <[email protected]> wrote: > > By deprecate I hope you don't mean remove. This change would break > > almost every single wicket application ever written. > > Yes I do mean remove. And yes that will break a lot of > applications, and that is why we have semantic versioning, so that we > can break with the past and get something better in place. > > We do need to make it better than the thing we currently have. That is the > intention of this RFC and the process I want us to go through: to get > all (or at least most) the usecases on the table, and to specify how the > new vision will work before it is implemented. Of course the devil is > always in the implementation, but I want the user side to be clear as > possible. > > I want this RFC to be so damn good that your fingers itch to upgrade to > Wicket 7 so you can exorcise all PageParameters processing from your > pages. > > Martijn >
