[ https://issues.apache.org/jira/browse/WICKET-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Long updated WICKET-4707: ------------------------------- Description: There is some duplication of functionality between the ResourceReference and HeaderItem layers. ResourceReferences should not be responsible for managing header contribution dependencies. This is the job of HeaderItem. ResourceReference's job is to provide a reference to a IResource. In that context, getDependencies() unnecessary. ResourceReference is the layer below HeaderItem, but implementation problems of HeaderItem have crept into the lower layer. In the same vein, IJavaScriptLibrarySettings should manage HeaderItems, not ResourceReferences. It is concerned with making sure that the correct header contributions have been made for the various Javascript things to work. This can be done entirely without ResourceReferences, but not without HeaderItems. The important things is the header items. Working on some patches... was: There is some duplication of functionality between the ResourceReference and HeaderItem layers. ResourceReferences should not be responsible for managing header contribution dependencies. This is the job of HeaderItem. ResourceReference's job is to provide a reference to a IResource. In that context, getDependencies() unnecessary. ResourceReference is the layer below HeaderItem, but implementation problems of HeaderItem have crept into the lower layer. In the same vein, IJavaScriptLibrarySettings should manage HeaderItems, but ResourceReferences. It is concerned with making sure that the correct header contributions have been made for the various Javascript things to work. This can be done entirely without ResourceReferences, but not without HeaderItenms. The important things is the header items. Working on some patches... > Remove ResourceReference.getDependencies() > ------------------------------------------ > > Key: WICKET-4707 > URL: https://issues.apache.org/jira/browse/WICKET-4707 > Project: Wicket > Issue Type: Improvement > Components: wicket > Affects Versions: 6.0.0-beta3 > Reporter: Jesse Long > Priority: Minor > > There is some duplication of functionality between the ResourceReference and > HeaderItem layers. > ResourceReferences should not be responsible for managing header contribution > dependencies. This is the job of HeaderItem. ResourceReference's job is to > provide a reference to a IResource. In that context, getDependencies() > unnecessary. > ResourceReference is the layer below HeaderItem, but implementation problems > of HeaderItem have crept into the lower layer. > In the same vein, IJavaScriptLibrarySettings should manage HeaderItems, not > ResourceReferences. It is concerned with making sure that the correct header > contributions have been made for the various Javascript things to work. This > can be done entirely without ResourceReferences, but not without HeaderItems. > The important things is the header items. > Working on some patches... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira