[
https://issues.apache.org/jira/browse/WW-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670030#comment-16670030
]
Yasser Zamani commented on WW-4974:
-----------------------------------
New findings: {{this.reloadingConfigs}} is always {{false}} in
{{DefaultFileManager.loadFile}} because Struts firstly loads with
{{DefaultConfiguration.reloadContainer()\{.. Container bootstrap =
this.createBootstrapContainer(providers); ..\}}} which is a bootstrap loader
with always hard-coded {{builder.constant("reloadXmlConfiguration", "false")}}
:( these mean Struts 2.5.18 never is able to build revision :(
Any idea? Maybe we have to use something else rather than
{{this.reloadingConfigs}} to decide to monitor or not monitor a file, but what
to use? how to decide? (Always monitoring files wakes up WW-4948 again)
> NullPointerException in DefaultStaticContentLoader#findStaticResource
> ---------------------------------------------------------------------
>
> Key: WW-4974
> URL: https://issues.apache.org/jira/browse/WW-4974
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.5.18
> Environment: Tomcat 9 on Ubuntu 18 Java 8 struts 2.5.18
> Reporter: nikos dimitrakas
> Priority: Major
> Fix For: 2.6, 2.5.19
>
>
> pathPrefixes is null. The defaults that were loaded correctly in previous
> versions are now not loaded. The method setHostConfig does not get called
> like in previous versions.
> This causes all js files to not be found. For example
> /struts/js/base/version.min.js
> /struts/js/base/jquery-2.2.4.min.js
> /struts/js/struts2/jquery.ui.struts2.min.js
> /struts/js/struts2/jquery.datatables.struts2.min.js
> /struts/js/plugins/jquery.dataTables.min.js
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
