[teiid-issues] [JBoss JIRA] (TEIID-2809) Support for property substitution in vdb.xml files

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-2809.
---------------------------------

        Labels: Alpaha2  (was: )
    Resolution: Done


If a "-vdb.xml" and "vdb.xml" file has any property values that are in the form

{code}
${my.property.name}
{code}

they will be replaced with defined system property by the same name during the deployment time of the VDB. The System property can be defined on the JBoss AS configuration or on startup command using -Dmy.property.name=foo.

Note that this only works in JBoss AS/EAP environments, not in embedded deployments. It is up to the user to do the property substitution in the embedded mode.
                
> Support for property substitution in vdb.xml files
> --------------------------------------------------
>
>                 Key: TEIID-2809
>                 URL: https://issues.jboss.org/browse/TEIID-2809
>             Project: Teiid
>          Issue Type: Enhancement
>    Affects Versions: 8.5
>         Environment: EAP 6.1 Alpha , Teiid 8.5
>            Reporter: Madhu Garimilla
>            Assignee: Ramesh Reddy
>              Labels: Alpaha2
>             Fix For: 8.7
>
>
> I have created a vdb.xml where i have declared my translators in it. I would like to pass some parameters to one of my translators so that i do not need to change my vdb.xml whenever there is a change in value. These parameters derive the values from the system properties. So, i am using ${} notation to pass the value of the system properties to my translator. When i try to deploy my VDB and try to access the parameters inside the translator, These system properties are not being resolved to the actual values. 
> As per the thread https://community.jboss.org/thread/236325, this is not being supported as of now and requires an enhancement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira