Would it break the API in 1.4.x? The Panel class isn't usable as a concrete class, so folks probably aren't doing new Panel() (and if they are, they shouldn't be). No big deal, really I guess.
On Wed, Dec 2, 2009 at 9:35 AM, Jonas <[email protected]> wrote: > I raised the same question a while ago: > > http://old.nabble.com/Panel-instances-ts25922356.html#a25922356 > > seems to be fixed in 1.5, but left as-is in 1.4 in order not to create > an api break > > cheers, > Jonas > > > On Wed, Dec 2, 2009 at 12:24 PM, Johan Compagner <[email protected]> wrote: >> I just got a question about: >> >> Markup of type 'html' for component >> 'org.apache.wicket.markup.html.panel.Panel' not found >> >> because it used a panel (but he meant to use in this example a >> WebMarkupContainer) >> But i think he shouldnt be allowed to say new Panel() at all... >> I would expect that it would be abstract just like Page or am i missing >> something obvious here? >> >> johan >> >
