Overriding the web-client-config for dashlets

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

simon

Hi Alf,

I'm using Alfresco 1.4.0 Enterprise and was playing with the dashlet configuration. I tried to define some custom JSP pages in the web-client-config file as showed in the wiki.

Now, when I add my code in the main web-client-config file it works:

<tomcat>/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/web-client-config.xml‍

If I add the same configuration in the extended configuration file (where it should be), it doesn't…

<tomcat>/shared/classes/alfresco/extension/web-client-config-custom.xml‍

This is my configuration (in the surrounding tags off-course):

  <dashlet id="dashlet1" label="dashlet1"
        description="First test dashlet"
        jsp="/jsp/extension/dashboards/dashlets/dashlet1.jsp" allow-narrow="false" />‍‍‍

Am I doing something wrong here? Anybody else with the same problem?

Thanks!

gavinc

This sort of problem is usually caused by there being multiple web-client-config-custom.xml files being present in the classpath.

If you have a web-client-config-custom.xml in another location i.e. in a JAR file or as I fell fowl of the other day in <tomcat>/common/classes/alfresco/extension/web-client-config-custom.xml then the other file might be getting picked up before yours.

You can turn on debugging for the config classes which should tell you if a web-client-config-custom.xml file is being read in and it should give you an indicate as to the elements it's reading which in turn may give some clues to where it is.

To turn on debugging use:

log4j.logger.org.alfresco.config=debug
log4j.logger.org.alfresco.web.config=debug

in your log4j.properties.

Hope this helps.