Show Table of Contents
10.11. Application Security
10.11.1. Enabling/Disabling Descriptor Based Property Replacement
Summary
Finite control over descriptor property replacement was introduced in jboss-as-ee_1_1.xsd. This task covers the steps required to configure descriptor based property replacement.
Descriptor based property replacement flags have boolean values:
- When set to
true, property replacements are enabled. - When set to
false, property replacements are disabled.
Procedure 10.37. jboss-descriptor-property-replacement
jboss-descriptor-property-replacement is used to enable or disable property replacement in the following descriptors:
jboss-ejb3.xmljboss-app.xmljboss-web.xml*-jms.xml*-ds.xml
The default value for
jboss-descriptor-property-replacement is true.
- In the Management CLI, run the following command to determine the value of
jboss-descriptor-property-replacement:/subsystem=ee:read-attribute(name="jboss-descriptor-property-replacement")
- Run the following command to configure the behavior:
/subsystem=ee:write-attribute(name="jboss-descriptor-property-replacement",value=VALUE)
Procedure 10.38. spec-descriptor-property-replacement
spec-descriptor-property-replacement is used to enable or disable property replacement in the following descriptors:
ejb-jar.xmlpersistence.xml
The default value for
spec-descriptor-property-replacement is false.
- In the Management CLI, run the following command to confirm the value of
spec-descriptor-property-replacement:/subsystem=ee:read-attribute(name="spec-descriptor-property-replacement")
- Run the following command to configure the behavior:
/subsystem=ee:write-attribute(name="spec-descriptor-property-replacement",value=VALUE)
Result
The descriptor based property replacement tags have been successfully configured.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.