EAP Patching: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
$JBOSS_HOME/modules/system/layers/base/.overlays/$PATCH_ID/$MODULE | $JBOSS_HOME/modules/system/layers/base/.overlays/$PATCH_ID/$MODULE | ||
</pre> | </pre> | ||
while the original files are left in | |||
<pre> | |||
$JBOSS_HOME/modules/system/layers/base/$MODULE | |||
</pre> | |||
The patching mechanism renders the original JAR files unusable, for security reasons. If the patch is rolled back, the original files will be reverted to an usable state. | |||
Revision as of 22:33, 15 March 2016
Internal
Relevance
- EAP 6.4
Overview
Patches are distributed as zip files or RPMs (for a subset of products).
Patching with zip files and patching with RPMs is incompatible, the same method should be used for subsequent patches.
After a patch is applied, the patched JARs are picked up at runtime from:
$JBOSS_HOME/modules/system/layers/base/.overlays/$PATCH_ID/$MODULE
while the original files are left in
$JBOSS_HOME/modules/system/layers/base/$MODULE
The patching mechanism renders the original JAR files unusable, for security reasons. If the patch is rolled back, the original files will be reverted to an usable state.