how to use “war.context” in Configuration file of Play Framework ?

by

Take a look at this thread on the Google Groups for a description of what you are asking.

http://groups.google.com/group/play-framework/browse_thread/thread/b4783c821fd29898?pli=1

In essence, what it is saying, is.

In your application.conf file, you set a property such as

war.context=/MyAppName

Then, in your routes file, you set it up to include your WAR context in the following way

# Set context name 
%{ ctx = play.configuration.getProperty('war.context', '') }% 

# Routes 
# This file defines all application routes (Higher priority routes first) 
# ~~~~ 
# Home page 
GET     ${ctx}/                                      Application.index 
# Map static resources from the /app/public folder to the /public path 
GET     ${ctx}/public/                               staticDir:public 
# Catch all 
*       ${ctx}/{controller}/{action}                 {controller}.{action}

You can see therefore, whatever you place in your war.context, you can then put into your routes to pick up the correct path.

More Related Contents:

  1. How do I change the default port (9000) that Play uses when I execute the “run” command?
  2. Adding Play JSON Library to sbt
  3. How do I run a Play Framework 2.0 application as a Windows service?
  4. Are there any benefits in using non-async actions in Play Framework 2.2?
  5. Understanding implicit in Scala
  6. How to use @Where in Hibernate
  7. Steps needed to use MySQL database with Play framework 2.0
  8. RESTful on Play! framework
  9. Play 2.4: Form: could not find implicit value for parameter messages: play.api.i18n.Messages
  10. Declare variable in a Play2 scala template
  11. Play: How to implement action composition
  12. How to use IntelliJ with Play Framework and Scala
  13. Play Framework 2: Read the application version defined in Build.scala
  14. How to serve uploaded files in Play!2 using Scala?
  15. Scala start Play server in production
  16. New object with HQL
  17. jQuery JSON response always triggers a ParseError

Leave a Comment