GitHub user cgdrake opened a pull request:
https://github.com/apache/felix/pull/120
[FELIX-4447] fix regexp, thanks to Olivier Fayau
git-svn-id: https://svn.apache.org/repos/asf/felix/trunk/scr@1591422
13f79535-47bb-0310-9956-ffa450edef68
Given that this is a low impact
[
https://issues.apache.org/jira/browse/FELIX-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173682#comment-16173682
]
ASF GitHub Bot commented on FELIX-4447:
---
GitHub user cgdrake opened a pull request:
Grzegorz Grzybek wrote
> Hello
>
> I like the idea of "only one PM is used" - or rather I don't like the
> idea of using a whole array of all available
> org.apache.felix.cm.PersistenceManager implementations.
>
> In my particular case I wanted to provide "encrypting file persistence
> manager"
Hello
I like the idea of "only one PM is used" - or rather I don't like the
idea of using a whole array of all available
org.apache.felix.cm.PersistenceManager implementations.
In my particular case I wanted to provide "encrypting file persistence
manager" - ideally I wanted to wrap existing
Hi
the current way of handling persistence managers in our config admin
implementation is not 100% reliable and ultimately can lead to confusion
and wrong results (see FELIX-5693 and FELIX-5685).
Now, I've suggested an improvement in FELIX-5693 which should solve the
problem and provides a 100%
[
https://issues.apache.org/jira/browse/FELIX-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-5693:
---
Assignee: Carsten Ziegeler
> Improve persistent manager handling
>
[
https://issues.apache.org/jira/browse/FELIX-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172966#comment-16172966
]
Carsten Ziegeler commented on FELIX-5693:
-
In rev 1808980 I moved the current mechanism to a
[
https://issues.apache.org/jira/browse/FELIX-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172958#comment-16172958
]
David Bosschaert commented on FELIX-5678:
-
bq. IIUC the API is no longer open for comments,