[
https://issues.jboss.org/browse/WFCORE-2564?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2564:
------------------------------------------
Thoughts on how this should be done:
1) PathManager should expose a new resolveRelativePathEntry(String path, boolean
possiblyAbsolute, String relativeTo) method, wherein if the possiblyAbsolute param is
true, an absolute path check is performed on 'path' and if it's absolute
relativeTo is ignored. AbstractPathService.isAbsoluteUnixOrWindowsPath(String path) is the
check.
This would let the kernel handle this kind of thing instead of extensions coding it
themselves the way the AS7-5600 fix had to be done.
2) ResolvePathHandler.Builder should add a setter to let callers set a possiblyAbsolute
value, which then gets passed into ResolvePathHandler, which uses it to call PathManager.
3) Default is 'false' consistent with current behavior.
Customize resolve-path handle to handle absolute paths
------------------------------------------------------
Key: WFCORE-2564
URL:
https://issues.jboss.org/browse/WFCORE-2564
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Beta9
Reporter: Jeff Mesnil
Assignee: Brian Stansberry
The :resolve-path operation will always resolve the path based on the relative-to
attribute.
In the messaging subsystem, we have a different behaviour where the relative-to attribute
is *ignored* (whether it is defined or not) when the path value correponds to an absolute
path.
To be consistent with this behaviour, the :resolve-path operation builder would need
customization and specify that the relative-to attribute must be ignored when the path is
absolute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)