It looks like Wicket 1.5 is a so radical change to 1.4 that it better would have been named Wicket 2. Nevertheless, creating an intermediate version which deprecated the old classes and methods but information/code about how to migrate to the new API would have MUCH better approach. If 1.4 to 1.5 requires to rewrite half of the application, I fear for Wicket 2. Maybe it will require the use of a different programming language?
Tom On 07.02.2012 16:51, Bertrand Guay-Paquet wrote: > I think you need to create your own subclass of WebMarkupContainer which > overrides Component#newMarkupSourcingStrategy() to return the proper > IMarkupSourcingStrategy. > > > On 07/02/2012 10:46 AM, Thomas Singer wrote: >> We subclassed WebMarkupContainerWithAssociatedMarkup and used it as >> Component. Neither of your suggested IMarkupSourcingStrategy implementations >> is a Component. What should I do? Thanks in advance. >> >> Tom >> >> >> On 07.02.2012 13:26, Martijn Dashorst wrote: >>> On Tue, Feb 7, 2012 at 1:18 PM, Thomas Singer<[email protected]> wrote: >>>> The migration guide mentions WebMarkupContainerWithAssociatedMarkup in the >>>> section TabbedPanel, but there is not such class in Wicket 1.5 any more. >>> See IMarkupSourcingStrategy and its implementations. >>> >>> Martijn >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
