Play2 Application on Wildfly: Why and How
JavaEE (v5 and v6) has a commanding presence in both marketshare and (developer) mindshare in the enterprise software world. The specifications are well thought-out, battle-tested and highly relied upon. I started using JavaEE (v5) way back in 2007 with JBoss 4.x. The latest release, JavaEE-7, which was released close to a year ago brings with itself a lot of worthy changes to the specs and impl. To bring myself up to speed on it I went through few books and attended a conference (JUDCon, Bangalore). But I have also been coding and acquainting myself with Typesafe’s Scala reactive stack. These two stacks are bound to compete with each more and more in the coming days. However I feel, they can be used in applications in complementary ways when carefully designed. The competition and challenge to JavaEE-7 stems from two tough requirements -
- Horizontal scalability
- Near real-time persist/process/view of ever increasing data volumes
The JavaEE stack is broadly split into 3 tiers - web, business and persistence. JSF (broadly, including expression-lang, JSTL, JSP and Servlets) is the technology of choice (per the specs) in the web tier. And JSF, to me, seems most vulnerable of not being able to raise up to the above mentioned two challenges. JSF does feel like the loose brick in the JavaEE stack. And it feel ever more so after spending some time with the Play Framework!
Web Tier In JavaEE - The Loose Brick?
This was a recent tweet by Peter Thomas -
Now to a quick primer on frameworks in JavaEE’s web-tier. I like to group the Web Tier of JavaEE applications into 3 groups per a broad grouping of library’s goals. A quick note on each of these…
- Component Frameworks:
- Component frameworks like JSF are suited for parts of the application with lot of forms and CRUD operations. JSF is an aggregate of multiple technical pieces which include facelets, expression language, jstl, converters, listeners, validators etc. JSF helps build composable UI components with server side validation in a scalable way
- It abstracts away a lot of state information in its stack which is not good for building UI components that serve a lot of read only and voluminous data. Tasks like JSON transformation within JSF are not efficient at scale
- Now, rarely do programmers get completely satisfied with the component library within JSF. So they use the richer component frameworks (above and beyond JSF) like Apache Wicket and Tapestry. And for dynamic pages with lot of AJAX there are frameworks like RichFaces and PrimeFaces which provide features atop JSF
- Action Frameworks: For read-only and voluminous data handling atop servlets action frameworks are preferred which explicitly tie to the HTTP request/response cycle. Action frameworks typically implement the famous MVC pattern for clear separation of concerns. So applications tend to use frameworks like Struts, SpringMVC etc
- Standalone, Proprietary Frameworks: These are the ones that are unbelievably beautiful for quick-small projects and unbelievably ugly for large ones. Technologies like JSP, GWT, Dart et al. These are just pure evil from enterprise products perspective
With me having done quite a bit of programming in JSP and JSF, I found Play to be fresh breath of air. Web application programmers must spend some time reading and understanding this blog by Guillaume Bort on reasons behind the decision to not write yet another framework atop Java’s HttpServlet. My experience with Play has been by building a lookalike for my blog with it (hosted on Heroku here). I have built my blog on NodeJS and RubyRails as well - and honestly, it took much lesser time to build it with Play. But more important is the question of should enterprise web-tiers be programmed with Play? Is Play up to the mark for projects of development scale and complexity? My answer is a thumping YES!!
Let me list the specific features that I found especially useful and important -
- Scala templating with compile time type safety - I have found UI composition to be very intuitive and much simpler than JSF (JSF’s composability really feels like a mess when compared with Play!)
- Crisp way to program with Futures and Async to handle action endpoints
- Websockets - Futures, Async - much better API for streaming data than the WebSocket Spec in JavaEE
- Stateless. Easy to use with Akka
- Marshalling/unmarshalling of JSON data without reflection which provides huge performance improvement
- Explicit, clean server side routing methodology (what a mess this is in JavaEE where programmers often mix annotations, xml and sometimes also bring in client-side routing unnecessarily)
- No server side sessions at all! Sessions in Play are all made available through cookies and HTTP headers. So no server side context to worry about
- Less verbose Scala code. The joy of composable functional programming
- Hot deployment during development
- Netty underneath - performance not an issue
- Cloud deployment ready (Heroku, Cloudbees support it)
This one is a excellent presentation (and code) by Yevginy Brikman of LinkedIn (LinkedIn uses Play! for multiple web apps in its stack). The title is apt - building web apps that are composable and streamable. More and more, enterprise applications have UI requirements of the kind described here. And building these using JSF/Java would be too complex a web project and IMHO not worth the trouble!
HOWTO - Play2 on Wildfly to interop with JavaEE
For very good reasons enterprise applications are generally hosted on application containers. And application containers mostly come built with a servlet container for web frontend. Now since Play2 is not Servlet based does it mean using it in enterprise applications straightaway get vetoed? Not necessarily. If engineers have a little chutzpah, the gap can be bridged. Here is how I was able to host my Play2 application on JBoss-Wildfly -
- The plugin to study and use for the task is the Play2War. Play2War builds a WAR out of a Play2 application. I was then able to deploy this WAR of my Play app on Wildfly and get it to work
After following the usage/configuration instructions from the Play2War’s GitHub page, the first thing to do is to configure the excludes. A number of JARs that get packaged using Play2War clash with JBoss’s modules and thus need to be excluded. Here is a quick list of such JAR’s from my project -
Artifact GroupID Version In Play v2.2.1 Version In Wildfly v8.0.0-Final Newer Google Guava com.google.guava 14.0.1 16.0.1 Wildfly Jackson Core, Annotations and Databind com.fasterxml.jackson.core.jackson v2.2.2 v2.3.0 Wildfly H2 Database com.h2database.h2 v1.3.172 v1.3.173 Wildfly Apache Commons Codec org.apache.commons.codec v1.6 v1.9 Wildfly Apache Commons IO org.apache.commons.io v1.3.2 v2.4 Wildfly Netty io.netty v3.7.0 v4.0.15 Wildfly Hibernate Commons Annotations org.hibernate v4.0.2 v4.0.4 Wildfly Hibernate Core, Entity Manager org.hibernate v4.2.3 v4.3.1 Wildfly Hibernate Validator org.hibernate v5.0.1 v5.0.3 Wildfly Javaassist org.javaassist v3.18.0 v3.18.1 Wildfly JBoss Logging org.jboss.logging v3.1.1 v3.1.4 Wildfly JBoss Transaction javax.transaction.api v1.0.0 v1.0.1 Wildfly Yaml org.yaml.snakeyaml v1.12 v1.13 Wildfly
Antlr org.antlr v2.7.7 v2.7.7 Same dom4j org.dom4j v1.6.1 v1.6.1 Same Postgres org.postgres v9.1-901 v9.1-901 Same javax.validation v1.1.0 v1.1.0 Same Joda time org.joda.time v2.2 v1.6.2 Play Apache Commons Lang org.apache.commons.lang v3.1 v2.6 Play HttpCore org.apache.httpcomponents. v4.3.1 v4.2.1 Play HttpClient org.apache.httpcomponents. v4.3.2 v4.2.1 Play Hibernate JPA javax.persistence.api v1.0.1 v1.0.0 Play Asm asm.asm v4.1 v3.3.1 Play jcl-over-slf4j org.slf4j v1.7.5 v1.7.2 Play jul-to-slf4j org.jboss.logging v1.7.5 v1.0.1 Play slf4j-api org.slf4j v1.7.5 v1.7.2 Play Xerces org.apache.xerces v2.11 v2.9.1 Play
One can see from the above table that versions of many artefacts is newer in Wildfly. I decided to use the newer Wildfly versions and exclude these from the WAR generated by Play2War. So included this filtering statement in my project’s build.sbt file -
Play2WarKeys.filteredArtifacts ++= Seq( (“com.google.guava”, “guava”), (“com.google.code.findbugs”, “findbugs”), (“com.fasterxml.jackson.core”,“jackson-annotations”), (“com.fasterxml.jackson.core”,“jackson-core”), (“com.fasterxml.jackson.core”,“jackson-databind”), (“com.fasterxml”,“classmate”), (“commons-codec”,“commons-codec”), (“commons-io”,“commons-io”), (“org.hibernate”,“hibernate-commons-annotations”), (“org.hibernate”,“hibernate-core”), (“org.hibernate”,“hibernate-entitymanager”), (“org.hibernate”,“hibernate-validator”), (“org.hibernate.common”,“hibernate-commons-annotations”), (“org.hibernate.javax.persistence”,“hibernate-jpa-2.0-api”), (“javax.validation”,“validation-api”), (“javax.persistence”,“persistence-api”), (“javax.transaction”,“transaction-api”), (“org.jboss.spec.javax.transaction”,“jboss-transaction-api_1.1_spec”), (“org.jboss.logging”,“jboss-logging”), (“org.jboss.logmanager”, “log4j-jboss-logmanager”), (“org.springframework”,“spring-beans”), (“org.springframework”,“spring-context”), (“org.springframework”,“spring-core”), (“postgresql”,“postgresql”), (“org.javassist”,“javassist”), (“org.yaml”,“snakeyaml”), (“antlr”,“antlr”), (“com.h2database”,“h2”), (“dom4j”,“dom4j”), (“tyrex”,“tyrex”) //(“com.jolbox”, “bonecp”), //(“io.netty”,“netty”), )
Next thing to do is to use a jboss-deployment-structure.xml where one can specify the newer Wildfly modules of these artefacts to be used for the deployment. This deployment descriptor should be created in the following path in the Play2 project -
app/ conf/ project/ war/ |–WEB-INF |–jboss-deployment-structure.xml
I used the following setting in this xml -
<jboss-deployment-structure> <deployment> <dependencies> <module name=“com.google.guava”/> <module name=“com.fasterxml.jackson.core.jackson-annotations”/> <module name=“com.fasterxml.jackson.core.jackson-core”/> <module name=“com.fasterxml.jackson.core.jackson-databind”/> <!–module name=“com.h2database.h2”/–> <module name=“org.apache.commons.codec”/> <module name=“org.apache.commons.io”/> <!–module name=“io.netty”/–> <module name=“org.hibernate.commons-annotations”/> <module name=“org.hibernate”/> <module name=“org.javassist”/> <module name=“org.jboss.logging”/> <module name=“org.yaml.snakeyaml”/> <module name=“org.antlr”/> <module name=“org.dom4j”/> <module name=“org.postgres”/> <module name=“javax.validation.api”/> <module name=“javax.persistence.api”/> <module name=“javax.transaction.api”/> <module name=“org.glassfish.javaeetutorial.helloservice-api”/> <module name=“org.jboss.log4j.logmanager”/> </dependencies> </deployment> </jboss-deployment-structure>
I wanted to use Hibernate in my Play project. And I wanted to interact with EJB’s and ActiveMQ messaging service in Wildfly. Firstly, this is very much possible. To use hibernate, one has to create the persistence.xml in the following structure -
war |–WEB-INF |–classes |–META-INF |–persistence.xml
Since the WAR will be deployed in Wildfly, make sure to read the persistence related docs from its wiki.
- Logging - Play2War’s GitHub wiki has a separate section for configuring logging with Wildfly. Make sure to read that. It basically asks for including this dependency in the build.sbt -
“com.github.play2war.ext” %% “redirect-playlogger” % “1.0.1”
- With this configuration the WAR built by Play2War for my Play2 project was around 50MB in size. One has to use JNDI lookup to access the EJB’s in container. The looked up EJB’s can be cached in a Scala Object to avoid repeats
- One shortcoming that I realised while doing this work was that websockets will not work in this setup. Play2 uses Netty as is HTTP server and Wildfly uses Undertow. The websocket implementation in Wildfly (per the Websocket 1.0 spec) could be closely tied to to Undertow - but I have not read Wildfly’s code to say so with certainty. Or maybe if one can make Wildfly to use Netty instead of Undertow as the underlying HTTP server then the websocket communication as provided by Play2 should become naturally available. Anyway, this is one shortcoming one has to put up if one takes this route
The Final Word - I really feel Play2 will be a really good fit even in the JavaEE stack a few years down the line when some more bridges will appear around it to make it easily compatible to JavaEE application servers. It can be done even now as I found out. However one should take this plunge very cautiously (at least when using Wildfly). But to me, this is the right way to go… and the right way is generally never easy!
comments powered by Disqus