Weblogic 10 is a fully compatible J2EE 5 application server, and as a result, it is associated with JPA 1.0.
There are two small questions that will help launch Play on weblogics.
- Applying Oracle Patch to Support Weblogic JPA 2.0
- Adding a deployment descriptor property to prioritize class resolution from web-inf
Both are trivial, and the Play documentation should probably mark weblogic 10 as the goal of a working deployment.
To fix # 1 , open the following oracle link.
For lazy readers, add this ad at the top of wlserver / common / bin / commEnv.sh
export PRE_CLASSPATH=$MW_HOME/modules/javax.persistence_1.0.0.0_2-0-0.jar:$MW_HOME/modules/com.oracle.jpa2support_1.0.0.0_2-0.jar
for windows, wlserver / common / bin / commEnv.bat file
set PRE_CLASSPATH=%MW_HOME%/modules/javax.persistence_1.0.0.0_2-0-0.jar;%MW_HOME%/modules/com.oracle.jpa2support_1.0.0.0_2-0.jar
To fix # 2 , create the weblogic.xml file in the following location myplayapp / war / WEB-INF / weblogic.xml
<?xml version="1.0" encoding="UTF-8"?> <weblogic-web-app> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app>
The war folder is automatically captured by play war when creating a web archive.
What is it!
I personally think that Play should create weblogic.xml itself, but thatโs not how it works with 1.2.1
source share