(25782972) Deployment fails on WebSphere Application Server 9 with StateChangeException.
There is a known issue with WebSphere Application Server 9 where an exception will occur when starting an application. This exception message is a service.state.StateChangeException. Refer to the IBM Support page for WebSphere for additional information.

Workaround: Add to custom JVM properties to the server to disable implicit bean scanning:

com.ibm.ws.cdi.enableImplicitBeanArchives=false
com.ibm.ws.cdi.enableDCI=false

(13301400) Inclusion of a welcome file on IBM WebSphere Application Server yields an error.
For example, a JSP that contains this dsp:include tag:

<dsp:include src="/" otherContext="/somecontext"/>

yields an error, as the dsp:include tag first flushes the response output stream, then WAS tries to resolve the welcome file by performing a forward, but the servlet spec prohibits performing a forward after output has been committed to the client.

Workaround: Specify the exact welcome file resource rather than just the directory.

(13287159) runAssembler -run-in-place option no longer accesses WAR files in the Oracle Commerce Platform installation.
The runAssembler -run-in-place option now requires that any WAR files in an application be deployed to the JBoss directory structure, rather than being accessed directly from the ORACLE COMMERCE PLATFORM installation. This means that if you make changes to a WAR file in the Oracle Commerce Platform installation, those changes are no longer immediately available.

Workaround: To make your changes available, call runAssembler -run-in-place again, so that the modified WAR file is redeployed.