Van and I were wondering what the near future needs are for per-office
configuration for a number of configuration settings normally set only
at install time. Emily confirmed from the PM perspective that some
time ago there were plans to support these settings on a per-office
basis, but the feature was cut and there is no current need for such
functionality.
Here's an example (from AccountBO) where a per-office configuration is
fetched, but the configured value returned is only ever defined for
the head office:
public boolean isBackDatedTrxnAllowed() {
return Configuration.getInstance().getAccountConfig(
getOffice().getOfficeId()).isBackDatedTxnAllowed();
}
In this case, the correct action would be to instead call
AccountConfig.isBackDatedTxnAllowed(), which reads the configuration
directly from the system-wide configuration file,
applicationConfiguration.default.properties. Note that
applicationConfiguration.default.properties is meant to never be
changed; per-deployment customizations should be added to
applicationConfiguration.custom.properties.
applicationConfiguration.custom.properties should be created (in the
same directory as applicationConfiguration.default.properties) if it
doesn't exist.
--
Adam Monsen
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
