Details
Description
While pax-wicket is consistence in loading panels and similar resources there's a logical flaw in loading resources and page-extensions (extends BasePage). It have to be validated if there it is possible to load header resources (css, js, ...) in a more osgi like way. In addition the same is valid for abstract base-pages. This is a typical way of working with things in wicket, but it would break the current model (although it works).
For the moment I've no idea how we can solve this (--> not assigned to 1.0.0 by now). Any ideas here?

still any ideas are welcomed here! I set this for now to unassigned...