When tested CUBA WAR deployment to Wildfly 12 found following documentation several problems:
The first problem : Execution of the following comand using Jbos-CLI fails, as there is no org/postgres module
When the postgresql.jar is put to deployments it is not added to modules.
Installation of the driver as a module is not required - it is available right after deployment. Or we should to describe how to install the driver as module.
**Note: Wildfly 13 has a bug and "test connection" everytime fails for a postgres datasource.
The second problem: no need to set includeJdbcDriver = true in the buildWar task, as the driver is already there.
The third problem: Modification of /opt/wildfly/standalone/configurations/standalone.xml config is required
Add to the <subsystem xmlns="urn:jboss:domain:logging:4.0"> snipet
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'entityManagerFactory' defined in class path resource [cuba-sp
ring.xml]: Invocation of init method failed; nested exception is java.lang.Class
CastException: org.slf4j.impl.Slf4jLogger cannot be cast to ch.qos.logback.class
ic.Logger
The fourth problem: Hibernate module is created only after jbos-cli is called. When a user runs the manual at first time there is no such module at the moment we asking him to replace the jar.
Environment
Description of the bug or enhancement
When tested CUBA WAR deployment to Wildfly 12 found following documentation several problems:
The first problem : Execution of the following comand using Jbos-CLI fails, as there is no org/postgres module When the postgresql.jar is put to deployments it is not added to modules.
Installation of the driver as a module is not required - it is available right after deployment. Or we should to describe how to install the driver as module. **Note: Wildfly 13 has a bug and "test connection" everytime fails for a postgres datasource.
The second problem: no need to set
includeJdbcDriver = true
in the buildWar task, as the driver is already there.The third problem: Modification of
/opt/wildfly/standalone/configurations/standalone.xml
config is requiredAdd to the
<subsystem xmlns="urn:jboss:domain:logging:4.0">
snipetIf not do do so the following exception occurs
The fourth problem: Hibernate module is created only after
jbos-cli
is called. When a user runs the manual at first time there is no such module at the moment we asking him to replace the jar.