using environment variabiles in deployment descriptors (web.xml, faces-config.xml, etc.) ?

[demanzano]

Hello,

I'm using Wildfly (15.x at the moment) in Docker containers and I found that environment variables can't be used in app descriptors like web.xml (i.e. for defining the data source credentials, etc.).

This is quite inconvenient

I know it already supports ${env.*} for its own XML files, unfortunately it's not enough in this situation.

(neither resolving them at packging time with Maven)

Would be possibile to add the support into next WF version ? Other appservers already have it.. (like the fish-named one )

Thanks!

Ale

[jaikiran]

This needs to be explicitly enabled in the domain/standalone configuration. The configuration to enable this feature is explained here WildFly Admin Guide

[demanzano]

Thanks for quick answer !

I did not know about these settings, they are indeed very useful but unfortunately are disabled by default..

If I enable the <spec-descriptor-property-replacement/> I can use either ${env.ENVVARNAME} or ${CMDLINEVARNAME}  where the latest is on the "standalone.sh" command line as "-DCMDLINEVARNAME=foo", great !

Now I only miss how to enable the <spec-descriptor-property-replacement/> in my container without copying an entire standalone.xml file ... Can I override it too from cmdline ?

many thanks!

Ale

[simkam]

I think it's not possible to override it with command line parameter when starting server, but you can use jboss-cli and connect to running server and run command

/subsystem=ee:write-attribute(name=spec-descriptor-property-replacement, value=true)