Affects: Release Notes
Workaround: Workaround Exists
Workaround Description: This workaround reflect changes needed to make booking sample work on ExP:

0/ Install Play! 1.0.3.2, append play binary to your $PATH
1/ Go to samples-and-tests/booking
2/ play war -o /tmp/booking.war
3/ add jboss-web.xml to WEB-INF directory for classpath isolation

{code}
<jboss-web>
   <class-loading>
      <loader-repository>
         org.jboss.wfk.example:archive=play-booking.war
         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
      </loader-repository>
   </class-loading>
</jboss-web>
{code}

4/ Remove following jars from WEB-INF/lib: slf4j-log4j12-1.5.10.jar
5/ Deploy exploded war to $JBOSS_HOME/server/$JBOSS_DOMAIN/deploy
securitylevel_name: Public

Applications generated with Play! framework can be deployed in exploded form on JBoss ExP after a war archive is created.

However, if user want to use persistence (I tried booking sample from the distribution), the Play! has hard dependency to JPA2, which is incompatible with EAP, EWP.

Workaround is to downgrade to Play! 1.0.3.2, however this version does not support injection of DataSource via JNDI.
Following code is working for 1.1.1, but not for 1.0.3.2, which is the latest JPA1 compatible release.
{code}
db=java:DefaultDS
{code}