framework play 2.2.1 Jboss - deployment

I can't deploy a play application framework 2.2.1 in JBoss.
I must do an application that communicates with EJBs and deploy into the same application server JBOSS.
the only way I have found is to use the start command.

You have to use the play war plugin, that will allow you to package your play app as a regular java web archive.
You can find the project here: https://github.com/dlecan/play2-war-plugin

Related

Is it possible to deploy akka-http to JBoss?

We are developing an akka-http application. Our infrastructure team requires us to deploy it to JBoss. Is it possible, if yes, how?
I found a plugin called xsbt-web-plugin, it converts a sbt application to a war file. That's all I have so far.

how to deploy a play 2.4.x framework web application in tomcat?

Appreciate if anyone can point to any resources that describes the steps to build a war for play 2.4.x framework and can be deployed to tomcat 7 or 8. I saw play2war plugin. I am not sure if this will work. Are there any other way to build a war and deploy to tomcat 7/8? Ultimately, I need to deploy it to aws elasticbeanstalk.
Thanks all for your help.

Scala and play 2 framework hosting what are the requirements

I am new to scala and play 2 framework and would like to know if they can be hosted on a webhost that has Tomcat, JSP, and Java Servlet hosting. I would obviously include the scala files.
Per the documentation, all you need on your server is JRE6 or later. Play does not use Tomcat, JSP or Java Servlets. Play will create a standalone distribution for you with the play dist command. Copy that to a server with Java installed and you're ready to go.
https://www.playframework.com/documentation/2.3.x/ProductionDist

How to deploy a Scala Play framework API using the SBT native packager

I created a web API based on the Scala Play framework 2. In the past I generated war files using a SBT plugin in order to deploy in production using Tomcat. It is now possible to build native package from Play project using the SBT native packager plugin. I used it to generate a debian package from my web app.
However, I don't understand how it works. I could generate and install the debian package and start the daemon, but my API seems not listening request.
In the first case, Tomcat hosts the war file which contains the Play app and manages the HTTP connection. I have the feeling that there are missing parts in my debian package in order to work properly like the war file under Tomcat.
The question is, how can I use the native packager plugin to deploy a standalone HTTP API? What is responsible to handle HTTP connection? What is missing in my project?
Thanks in advance
Play applications run using their own light weight http server.
To build a standalone project issue
sbt dist
or if your using activator
activator dist
This makes a directory target/universal/your-app.zip
If you unzip the contents you will find a standalone application structure
/bin
/lib
/conf
/share
under which you can find shellscripts that launch the server
bin/your-app
bin/your-app.bat (windows)
The distribution to a war file appears to have been removed from play. Similar question asked here:
Deploy play as a war file into a servlet container, even if it uses JPA heavily?

Build tool for Scala web application development

While working with Scala frameworks such as Play! and Lift I was really amazed how these frameworks manage to create a full development stack from the source code up to the web application container (Jetty).
Right now I'm trying to configure a project on my own with the following features:
Automatic deployment on Tomcat 7 (I'm not using Jetty as I require JEE6 support)
WAR file packaging
Is it possible to do it with a build tool such as SBT or Maven?
Note: My goal is to create my own project structure, not using an existing framework (even though I'm taking some ideas from them).
There is a web plugin for SBT:
https://github.com/JamesEarlDouglas/xsbt-web-plugin
It gives you war packaging, but not automatic deployment (other than on Jetty, which it integrates, but which you don't have to use).
That said, I'd like to see a fork of that plugin that removes the Jetty dependency and adds an automatic external deployment option. Shouldn't be too hard to do.