The migration guide mentions WebMarkupContainerWithAssociatedMarkup in the
section TabbedPanel, but there is not such class in Wicket 1.5 any more.
Tom
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
On Tue, Feb 7, 2012 at 1:18 PM, Thomas Singer wic...@regnis.de 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
--
Become a
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
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.
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
Hi Tom,
I have to admit that migration to 1.5 looks daunting at first, but there
aren't so many radical changes actually.
Maybe it will require the use of a different programming language?
Don't give us any ideas ;).
Sven
Am 07.02.2012 17:28, schrieb Thomas Singer:
It looks like Wicket
On Tue, Feb 7, 2012 at 5:28 PM, Thomas Singer wic...@regnis.de wrote:
It looks like Wicket 1.5 is a so radical change to 1.4 that it better would
have been named Wicket 2.
The whole request processing part has been rewritten. The whole URL
generation/parsing has been rewritten. But that is the
