Glassfish and payara allow for variables to be specified in deployment descriptors and annotation equivilents. This is documented here
This is non-portable if used, but it does mean that you can override the configuration at deployment time. In Liberty this is done by doing an override of the deployment descriptor in server.xml, but allowing variable substitution would be an alternative that might be simpler, especially in fat jar or docker deployment scenarios.
The text was updated successfully, but these errors were encountered:
Closing since we found an alternative solution for the original issue that prompted this and we have significant concerns about how safe doing this would be.
I found this issue because I wanted this exact feature. For me the reason is that in local development my eclipse IDE will edit the server.xml with an tag once I 'add' my EAR project to the server. So if I need for instance an application-bnd tag with security-roles, I would have to do that manually. But if I put these tags in the ibm-application-bnd.xml, I can't use variables for something that is environment specific like the group name=".." attribute.
Now my questions are:
is this similar to the original issue that you refer to?
Glassfish and payara allow for variables to be specified in deployment descriptors and annotation equivilents. This is documented here
This is non-portable if used, but it does mean that you can override the configuration at deployment time. In Liberty this is done by doing an override of the deployment descriptor in server.xml, but allowing variable substitution would be an alternative that might be simpler, especially in fat jar or docker deployment scenarios.
The text was updated successfully, but these errors were encountered: