Hi, i was wondering why CssUrlReferenceHeaderItem (wicket 6.2.0) is implemented by HeaderItem#getDependencies() which returns an empty list. The CssReferenceHeaderItem has a getDependencies implementation which uses the dependencies provided by the resource reference.
If i extend CssUrlReferenceHeaderItem (for testing) and provide the dependencies of the resource reference (analogoues to CssReferenceHeaderItem) everything works fine. But maybe i miss here something. So my question is: Is it required that CssUrlReferenceHeaderItem is not handling dependencies of the resource reference? Thanks for explanation. Per --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
