...
| Code Block |
|---|
| title | jboss-deployment-structure.xml |
|---|
|
<exclude-subsystems>
<subsystem name="jaxrs" />
<subsystem name="resteasy" />
</exclude-subsystems> |
Deployment options
Deploying a WAR
To deploy the downloaded Magnolia WAR file to WildFly:
...
| Info |
|---|
 WildFly unpacks .war files to a tmp directory and deletes the directory as part of the shutdown process. This means that every time WildFly restarts, the Magnolia webapp forgets everything – modules, repository, license key. To get around this issue, you can deploy the Magnolia webapp as an extracted (unpacked) directory or configure Magnolia to store the repository outside the tmp directory. Alternatively, specify the following paths in your magnolia.properties configuration. If you point the paths outside of WildFly's tmp directory, Magnolia will not reinstall on every startup and they will not be deleted on every shutdown.
| Code Block |
|---|
magnolia.home=/somewhere_outside_of_wildfly_tmp_folder
magnolia.cache.startdir=${magnolia.home}/cache
magnolia.upload.tmpdir=${magnolia.home}/tmp
magnolia.exchange.history=${magnolia.home}/history
magnolia.repositories.home=${magnolia.home}/repositories
magnolia.logs.dir=${magnolia.home}/logs |
|
To deploy an extracted directory:
...