Let's say you encounter an error halfway through the constructor of a
page,
and you want to display error(error message) and then return without
processing rest of components? It doesn't seem like this is possible
in
wicket because it makes you fill in all components or else it barfs.
Am I
Let's say you encounter an error halfway through the constructor of a page,
and you want to display error(error message) and then return without
processing rest of components? It doesn't seem like this is possible in
wicket because it makes you fill in all components or else it barfs.
Am I
you would have to fill in the component hierarchy. i suppose you could fill
the rest of the components as invisible webmarkupcontainers, but this sounds
very cumbersome. My typical mode of operation for this sort of thing is to
do this:
getSession().error(your error)
throw new
