Transit resource hosts configuration allows the declaration of a host layout scheme. Layout schemes deal with the mapping of a resource identifier to a resource location. Three layout schemes are provides as a part of the core Transit system together with support for the installation of custom layout handlers. The standard layout schemes supported within the Transit core system are described below.
The ModernLayout decodes artifacts into a layout scheme that follows the [group[/[subgroup[/...]]]/[version]/name[-[version]].[type] convention.
| artifact: | artifact:jar:metro/cache/dpml-cache-main#1.0.0 |
| path: | [host]/metro/cache/1.0.0/dpml-cache-main-1.0.0.jar |
The ClassicLayout decodes artifacts into the Classic/Maven layout of artifacts on a file system or http server. This format says that for an artifact artifact:[type]:[group]/[name]#[version] the location of such artifact shall be: [group]/[type]s/[name]-[version].[type].
| artifact: | artifact:jar:metro/cache/dpml-cache-main#1.0.0 |
| path: | [host]/metro/cache/jars/dpml-cache-main-1.0.0.jar |
The EclipseLayout maps artifacts into the Eclipse specified layout of artifacts on a file system or http server. This format says that for an artifact artifact:[type]:[group]/[name]#[version] the location of such artifact shall be: [group]-[version]/[name].[type].
| artifact: | artifact:jar:metro/cache/dpml-cache-main#1.0.0 |
| path: | [host]/metro/cache-1.0.0/dpml-cache-main.jar |