On Thu, Apr 9, 2015 at 9:23 PM, Nick Pratt <nbpr...@gmail.com> wrote:

> Based on the wicket guide, since 1.5 the header contributions of children
> should occur before that of the Page they are contained in so that the Page
> can override any component contributions.
> Is this still valid?  We've got a case where a Panel is contributing a CSS


> file that's appearing in the final markup after that of the Page (which
> prevents our application level style sheet from overriding the component's
> added styles)  - is there a likely reason for this that we've overlooked?

A dependency?
See HeaderItem#getDependencies() and ResourceReference#getDependencies()

> N

Reply via email to