Configuration of search-max-results not respected

[frank_d]

Hi,

I have a difficult to understand problem with the configuration of the search in the web-client.

There are two configuration of the parameter search-max-results, one can be found in web-client-config.xml, the other in a custom .xml file that overrides some of the values in the default file:
<search-max-results>500</search-max-results>
<search-max-results>100</search-max-results> (overriden)

Regardless of both, the line in BrowseBean.java:

int searchLimit = Application.getClientConfig(FacesContext.getCurrentInstance()).getSearchMaxResults();

only returns -1.


Clearly there is something incorrectly configured.
My question:

1)Are there other files that might overrule the searchLimit value? I can find no files in my workspace with the same xml-tag, except for the two already mentioned.
2)Perhaps my config files are not being read or in the wrong order. Where can I see the loading of these config files happening?

thx,

F

[frank_d]

Further investigation shows it's nothing in the war-file, since the same WAR file on one system accepts the configured search limit value, while the exact same WAR file deployed on another system, does not.

That leaves some shared config files outside the tomcat alfresco directory as suspects, and also the repository itself which is also different on both systems.

I admit to total confusion…

F

[frank_d]

Found a small custom config file in Data Dictionary/Customized Web Client that seemed to override all others.

Wonder if that was because of something in the file itself, or if this is because of the LOCATION of the file in Data Dictionary/Customized Web Client?

Either way deleting that file restored the configuration of the search limit parameter.

I'll go look for a good place to learn about overwriting config options.

SOLVED