topic Re: Use of PropertyPlaceholderConfigurer in Alfresco Modules in Alfresco Archive

Use of PropertyPlaceholderConfigurer in Alfresco Modules

darryl_staflund — Fri, 12 Nov 2010 23:20:25 GMT

Hi there,I have spent the last couple of days moving some important configuration values out of the Spring context modules of my Alfresco AMPs into some property files. But when I try to make use of them using a PropertyPlaceholderConfigurer bean, the values defined in the files aren't found. I am

Re: Use of PropertyPlaceholderConfigurer in Alfresco Modules

hap234 — Mon, 15 Nov 2010 06:37:51 GMT

Check the key that you have give in property file.
my_module_id.job.workflow_report.minor_correction.cron=0 0/5 * * * ? *

And check the key that you have given in Spring bean reference.

<property name="cronExpression" value="${my.package.job.workflow_report.minor_correction.cron}"

I think both are different which is the cause of this issue.
change either one to make it same as other will solve your problem.

Best Regards,
Hetal Patel,
CIGNEX Tech

Re: Use of PropertyPlaceholderConfigurer in Alfresco Modules

darryl_staflund — Mon, 15 Nov 2010 16:10:25 GMT

Hi Hetal,

Thanks for bringing the typo to my attention – it's not part of the code but was introduced when I anonymized my config values for display in the forum. I didn't catch the discrepancy. Sorry about that. It should be fixed now.

The problem remains though – Spring doesn't substitute property references with values read by the PropertyPlaceholderConfigurer class.

Darryl

Re: Use of PropertyPlaceholderConfigurer in Alfresco Modules

darryl_staflund — Fri, 19 Nov 2010 21:54:30 GMT

Hi everyone,

I have figured out how to read spring configuration properties on a project-by-project basis. It turns out that every PropertyPlaceholderConfigurer bean defined in a Spring application has to have a unique placeholder Prefix/Suffix combination – meaning that if you define two or more configurer beans using ${} as your placeholder syntax, only the values read by one of the beans will be used. This is why Alfresco kept throwing an exception when trying to process my bean definitions – it couldn't find the properties defined by my configurer bean because the placeholder syntax was mapped to another bean.

I was able to get it working using the following configurer bean:


    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="location" value="classpath:alfresco/module/module_id/module_id.properties" />
        <property name="placeholderPrefix" value="%{module_id:" />
        <property name="placeholderSuffix" value="}" />
    </bean>
‍‍‍‍‍‍‍

and the following placeholder references:


    <bean id="module_id_maxVersionPolicy" class="company.id.alfresco.common.policies.MaxVersionPolicy" init-method="init">
        <property name="maxVersionPolicyCandidateSpecification" ref="module_id_maxVersionPolicyCandidateSpecification" />
        <property name="policyComponent" ref="policyComponent" />
        <property name="versionService" ref="versionService" />
        <property name="maxVersions" value="%{module_id:policy.document_versioning.maxVersions}" />
    </bean>
‍‍‍‍‍‍‍‍

My resource file looks as follows:


policy.document_versioning.maxVersions=10
‍‍‍

Note that '${module:' won't work as a prefix because the '${' portion of the prefix causes Spring to map it to another configurer defined somewhere else in Alfresco. I don't use '#{' so as not to conflict with JSF. Since I have more than one module to support, I include the module id in the placeholder prefix.

I hope this is helpful to someone.

Darryl