History

Jens Pelzetter 4acde5a0ed Wildfly plugin configuration Former-commit-id: `24e252881b`		2020-06-19 12:24:29 +02:00
..
src	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00
.gitignore	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00
README.md	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00
datasource.example.properties	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00
nb-configuration.xml	CCM NG: Bundles are now EARs (necssary because otherwise JPA does not support entities in multiple JARs, see JSR-338, page 366f). Also the Foundry theming engine is now provided by its own Maven module.	2016-01-27 19:16:43 +00:00
package-lock.json	NPM Deploy is now working	2020-01-12 11:10:29 +01:00
package.json	JavaScript packages are now scoped	2020-01-09 09:59:56 +01:00
pom.xml	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00
pom.xml.releaseBackup	CCM NG: RESTful endpoints for the PageModel editor	2018-05-09 17:43:09 +00:00
tsconfig.json	CcmNG: Basic integration for TinyMCE	2018-09-01 17:00:13 +00:00
tslint.json	CCM NG: Working integration of NPM modules	2018-05-29 18:34:35 +00:00
webpack.config.js	CcmNG: Basic integration for TinyMCE	2018-09-01 17:00:13 +00:00
wildfly.example.properties	Wildfly plugin configuration	2020-06-19 12:24:29 +02:00

README.md

ccm-bundle-devel-wildfly README

This module creates a WAR which can be deployed to a Wildfly Application Server. For testing, the module also provides an runtime environment and the setup. The runtime is managed using the wildfly-maven-plugin.

At the moment the runtime only supports PostgreSQL as database.

To use these runtime some prepration steps are necessary.

Create the configuration files. The runtime is configured using two files:
- wildfly.properties allows it to configure the ports used by the Wildfly server
- datasource.properties provides the configuration data for datasource used by LibreCCM.
  
  For both files examples are provided (datasource.example.properties, wildfly.example.properties). Copy the example files and customize the settings is necessary.
Run a build using the setup-runtime profile. It is important to add the package goal, otherwise the WAR file which is deployed in this step is not build correctly:
```
mvn package -Psetup-runtime -pl ccm-bundle-devel-wildfly -am 
```
During the package phase of the this module Wildfly will be downloaded, unpackaged into the target directory, the PostgreSQL driver will be deployed, a datasource will be generated and the WAR file will be deployed.

To run LibreCCM in this environment, use the enable-runtime profile and the wildfly:start goal:

mvn -Penable-runtime -pl ccm-bundle-devel-wildfly wildfly:start

To shutdown the server:

mvn -Penable-runtime -pl ccm-bundle-devel-wildfly wildfly:shutdown