[
https://issues.apache.org/jira/browse/SLING-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454403#comment-15454403
]
Chetan Mehrotra edited comment on SLING-6021 at 9/1/16 5:52 AM:
----------------------------------------------------------------
One possibility is to make use of proposed ConfigurationPlugin enhancement [1]
and modify the properties at the time it is delivered to components. This can
then be implemented as a bundle in Felix project and can support constructs like
\$<prop-name>:<default>}
Where value can be looked from
# BundleContext
# System property
# Env property
[1]
https://github.com/osgi/design/blob/master/rfcs/rfc0227/rfc-0227-ConfigAdminUpdates.pdf
was (Author: chetanm):
One possibility is to make use of proposed ConfigurationPlugin enhancement [1]
and modify the properties at the time it is delivered to components
[1]
https://github.com/osgi/design/blob/master/rfcs/rfc0227/rfc-0227-ConfigAdminUpdates.pdf
> Supporting variable substitution in sling installer configuration factory
> -------------------------------------------------------------------------
>
> Key: SLING-6021
> URL: https://issues.apache.org/jira/browse/SLING-6021
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Affects Versions: Installer Configuration Factory 1.0.14
> Reporter: Ivo Leitão
> Priority: Minor
>
> I'm not completely sure if this is a new feature or not but I've not find any
> documentation that explains how to perform variable transformation in
> configuration resources.
> In my use case I want to configure Apache Aries Transaction manager (snippet
> bellow) and I would like to use the ${sling.home} environment variable
> aries.transaction.recoverable=true
> aries.transaction.timeout=600
> aries.transaction.howl.maxBlocksPerFile=513
> aries.transaction.howl.maxLogFiles=2
> aries.transaction.howl.logFileDir=${sling.home}
> aries.transaction.howl.bufferSizeKBytes=4
> Is it possible or this is a completly new feature ? (I' ve tested and it does
> not work)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
