You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2018/05/31 21:02:00 UTC
[jira] [Commented] (GERONIMO-6607) [geronimo-config] variable
replacement use cases
[ https://issues.apache.org/jira/browse/GERONIMO-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497167#comment-16497167 ]
Romain Manni-Bucau commented on GERONIMO-6607:
----------------------------------------------
[~struberg] any idea on how we can get it out before waiting new release? Im dependent on it already and i know some users not able to use it for the same reason so Id love to see it released asap.
> [geronimo-config] variable replacement use cases
> -------------------------------------------------
>
> Key: GERONIMO-6607
> URL: https://issues.apache.org/jira/browse/GERONIMO-6607
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Config
> Reporter: Mark Struberg
> Priority: Major
> Attachments: PlaceholdersTest.java
>
>
> While getting the geronimo-config/trunk and branches/ConfigJSR in sync, I've switched the PlaceholdersTest from using the internal Placeholders class to the official API.
> While doing so I figured that we should not yet add this functionality at all.
> But first we should discuss this through with mp and ConfigJSR.
> The reason is that variable replacement is already added in ConfigJSR but does not yet contain all the cases Romain has on it's wishlist.
> Plus we also need to ensure that we do not loose too much performance.
> A few of the replacement rules are quite a bit 'meta'.
> Before we implement those I really need the use cases first.
> I'll attach the pimped PlaceholdersTest
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)