[
https://issues.apache.org/jira/browse/FELIX-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897632#comment-17897632
]
Carsten Ziegeler commented on FELIX-6732:
-----------------------------------------
As this is for "edge cases" I think we should not go down this road. It also
comes then with the additional challenge that you need to make sure that all
post processors are available with the additional question what "all" means etc.
For edge cases it is probably fine to just fork the code base add any
additional processing and use that as a separate plugin
> Provide post processor hook for InterpolationConfigurationPlugin
> ----------------------------------------------------------------
>
> Key: FELIX-6732
> URL: https://issues.apache.org/jira/browse/FELIX-6732
> Project: Felix
> Issue Type: New Feature
> Components: Configuration Admin
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently the
> [InterpolationConfigurationPlugin|https://github.com/apache/felix-dev/blob/master/configadmin-plugins/interpolation/src/main/java/org/apache/felix/configadmin/plugin/interpolation/InterpolationConfigurationPlugin.java]
> cannot be extended. If one needs to add some post processing to the
> interpolated values one needs to come up with a completely new
> {{org.osgi.service.cm.ConfigurationPlugin}}.
> For some edge cases it would be helpful to plugin post processors (which kick
> in after doing the interpolation as provided by
> {{InterpolationConfigurationPlugin}} but before doing the type conversion
> (i.e. always acting on String values). I would propose to call all registered
> {{InterpolationConfigurationPluginPostProcessor}} services in order of their
> service ranking. The method signature could be a
> [UnaryOperator|https://docs.oracle.com/javase/8/docs/api/java/util/function/UnaryOperator.html].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
