WildFly Paths: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 39: | Line 39: | ||
In the above example, "<tt>hornetq.shared.dir</tt>" can be used as path name for "<tt>relative-to</tt>" used in HornetQ configuration. | In the above example, "<tt>hornetq.shared.dir</tt>" can be used as path name for "<tt>relative-to</tt>" used in HornetQ configuration. | ||
=Manipulating Paths with CLI= | |||
[[WildFly CLI - Manipulating Paths|Manipulating Paths with CLI]] | |||
=Directory Grouping= | =Directory Grouping= |
Revision as of 07:37, 28 February 2016
External
- EAP 6 Administration and Configuration Guide - Filesystem Paths https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-Filesystem_Paths.html
Internal
Overview
WildFly uses logical names for filesystem paths. All top-level configuration files standalone.xml, domain.xml and host.xml include a <paths> section for declaring paths. Closer declaration to the server take precedence.
WildFly Standard Paths
relative-to
"relative-to" attribute references a global path name in the domain model.
Adding Custom Paths
We can add more named paths, so we can use them as "relative-to". They are added as follows:
<server ...> <extensions> ... </extensions> <paths> <path name="hornetq.shared.dir" path="C:/tmp/hqd"/> </paths> ... </server>
In the above example, "hornetq.shared.dir" can be used as path name for "relative-to" used in HornetQ configuration.