Loading...

XML

Word

Printable

Affects:

Release Notes
Release Note Text:

Hide
When the <systemitem>jboss.vfs.forceCanonical</systemitem> property was set to <literal>true</literal>, VFS did not correctly cache <systemitem>VFSXXXContext</systemitem> objects for paths that included symbolic links. With this update, all symlinks are resolved to a path within the permanent root directory specified in the <systemitem>VFSCache</systemitem> bean defined in the <filename>$JBOSS_HOME/server/$CONFIG/conf/bootstrap/vfs.xml</filename> file, ensuring that the <systemitem>VFSXXXContext</systemitem> objects are now cached correctly.

Show
When the <systemitem>jboss.vfs.forceCanonical</systemitem> property was set to <literal>true</literal>, VFS did not correctly cache <systemitem>VFSXXXContext</systemitem> objects for paths that included symbolic links. With this update, all symlinks are resolved to a path within the permanent root directory specified in the <systemitem>VFSCache</systemitem> bean defined in the <filename>$JBOSS_HOME/server/$CONFIG/conf/bootstrap/vfs.xml</filename> file, ensuring that the <systemitem>VFSXXXContext</systemitem> objects are now cached correctly.
Release Note Status:
Documented as Resolved Issue
Docs QE Status:
NEW

VFS does not correctly cache VFSContexts for paths containing symbolic links in some scenarios when -Djboss.vfs.forceCanonical=true

is blocked by

JBVFS-166 Deployment archives that are symlinks do not get cached properly when jboss.vfs.forceCanonical is set to 'true'