#941 new
Gokul Kannan Jeyapaul

Context issues with Deployment in Tomcat

Reported by Gokul Kannan Jeyapaul | June 28th, 2011 @ 09:08 AM

Framework version: 1.2.1
Platform you're using: Windows

Reproduction steps:

  • Create a "sampleapp" in play
  • Create a war with play war sampleapp -o sampleapp.war
  • Deploy it in Tomcat
  • Try to run the URL - "http://localhost:8080/sampleapp"
  • Shows HTTP 404
  • The same app seems working fine in glassfish.

- Runs only in root context or isolation. But Tomcat is one of the widely used servers and it would be great to have this work with it. There is also an conflict with geronimo-servlet_2.5_spec-1.2.jar file.

Comments and changes to this ticket

  • Gokul Kannan Jeyapaul

    Gokul Kannan Jeyapaul June 28th, 2011 @ 04:33 PM

    Specifically occurs in Tomcat version 7.x. Seems to be working fine with Tomcat 6.x

  • Veronica J

    Veronica J June 12th, 2019 @ 05:50 AM

    Number of programming software’s you can use for the development and these are pretty helpful and can also improve your work efficiency as well. Pretty informative AssignmentHolic context issue solution update you discuss with experts reviews thanks for the help.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by