[
https://issues.apache.org/jira/browse/WICKET-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239514#comment-13239514
]
Martin Grigorov commented on WICKET-4471:
-----------------------------------------
Thanks for the clarifications!
With the last two comments it is more clear what you meant.
So in DEV mode an application can use package resources and for PROD mode the
app just need to add a bundle that main resref is ExternalUrlResRef and this
bundle will say "I'm responsible for some package resources" so the only
generated url is for the external resref. Sounds pretty good.
The example can contain the "external resource" in src/main/webapp, i.e. it
will simulate being external.
> Generic registry of javascript/css resource references
> ------------------------------------------------------
>
> Key: WICKET-4471
> URL: https://issues.apache.org/jira/browse/WICKET-4471
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.0.0-beta1
> Reporter: Ronald Tetsuo Miura
> Assignee: Emond Papegaaij
> Priority: Minor
> Attachments:
> 0001-WICKET-4471-unwrap-ResourceBundleReference-to-render.patch
>
>
> It would be nice if JavaScriptLibrarySettings had a generic mechanism to
> register javascript/css resource references (maybe using something like
> MetaDataKeys).
> This way, extension/third-party components (ModalWindow, DateTimeField, etc.)
> could register their resources, or just lookup for substitute resource
> references for their own scripts/stylesheets.
> This would allow some optimizations, such as minification/compression and
> joining many files into one, and hosting static files in CDNs.
--
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
