Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Whether Play2WarKeys.servletVersion := "2.5" is suitable for tomcat7? #316

Open
z07diac opened this issue Apr 3, 2017 · 3 comments
Open

Comments

@z07diac
Copy link

z07diac commented Apr 3, 2017

As the title, I used Tomcat 7.0.62 as contents.
I think the suggested Play2WarKeys.servletVersion is "3.0".
But if I use 3.0, the response of Application will be strange, such as twice response happen towards one request.
If I use 2.5, the application will work well.

So I have a question that whether it is OK if I use a 2.5 servletVersion on Tomcat7.

@yanns
Copy link
Member

yanns commented Apr 3, 2017

Yes you can use a 2.5 servlet version on Tomcat 7.
But it's be great to find out why you have such a misbehaviour with the 3.0 servlet.

@z07diac
Copy link
Author

z07diac commented Apr 3, 2017

@yanns Thank you so much for your reply.
Yeah, you are right. I will find out where is the problem.

@haroldoramirez
Copy link

haroldoramirez commented May 8, 2017

Hello,

I have the same problem and post a question on playframework-my-application-does-not-work-as-expected-on-apache-tomcat

The application has been sent to production and is working well. I am running on tomcat 8.

The settings and dependencies used are:

addSbtPlugin("com.github.play2war" % "play2-war-plugin" % "1.4.0")
Play2WarKeys.servletVersion := "2.5"

By typing the "activator war" command, the plugin create the file war/WEB-INF/web.xml and the file application.war.

I'm waiting to know what's wrong.

In the meantime servlet 2.5 is serving me as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants