playframework.com | The Play Framework website

When running sbt new playframework/play-scala-seed.g8 compiling and running from terminal everything works perfectly well. But when importing the project to IntelliJ, Adding a "Play 2 App" configuration, and running it, the program runs perfectly but stops immediately. Also, The play logo is shown twice.

I'm trying to start working with play framework. I tried using the "hello world" example for Java, but after running the "sbt run" command I get errors. I get a lot of lines in the CMD, with the last few lines being:

i hope someone can help me. I use following Code snippet to upload an image to my server (This is copied from here: https://www.playframework.com/documentation/2.8.x/ScalaFileUpload

Context: I'm trying to run the starter sample web application in the Play documentation for Scala: https://www.playframework.com/documentation/2.8.x/HelloWorldTutorial. I confirmed that I have the listed requirements and I've followed the instructions in the README which appear to state you run sbt run in the project directory. I'm raising a ton of errors which seem to indicate I have missing dependencies but I have no idea.

Questions: Can someone please assist in helping me interpret and resolve these errors? Thank you.

I do want to write some functional tests for our project. Techstack: Play Framework 1.5, Java 16, Junit 3.

I found following documentation: test - 1.5.x security - 1.5.x

So the Controller looks something like this.

Recently I switched my Play Framework-based project from Ehcache to Caffeine, because the Play documentation for version 2.8 says "For in-process caching Caffeine is typically the best choice."

Now, I implemented a little "test" to see how many items can be added to the cache before some items are evicted. The test simply adds more and more items to the cache (without an explicit expiration) in a loop, checking whether all previosuly inserted items still are available after each insert operation, until at least one previously inserted item is detected to be missing.

With Ehcache I found that the limit apparently is 10,000 items. After adding that many items to the cache, some "old" items start to disappear from the cache. So my conclusion is that Ehcache, by default, has a fixed size limit of 10,000 items. With Caffeine, on the other hand, there seems to be no limit at all! I kept the test running for a very long time, but even after inserting ~1 million items, still no previously inserted items had been evicted. At that point I stopped the test.

So, does Caffeine, unlike Ehcache, not have a size limit by default? Will it keep on accumulating items until, eventually, my application crashes with "out of memory" error, or is there some logic in Caffeine that evicts items in "low memory" situations? Is it advisable to configure an explicit cache size limit when using Caffeine? I would think so. But then, why Play doesn't do it by default?

Unfortuantely, the Cache documentation of Play Framework doesn't make clear at all which default settings Play uses with Ehcache and/or Caffeine. Also, a list of available Cache options in the Play configuration (and the respecitive default values) would be really helpful...

Regards.

I'm currently trying to create a class and subclasses that encapsulate various configuration aspects (provided in json) for a data pipeline; I'm still very much learning scala as well. I'm using the Play framework library in order to parse the json string input - https://www.playframework.com/documentation/2.8.x/ScalaJson

I have some code that currently works, but there are several aspects of it that feel wrong, and this does not feel like the correct approach.

The workflow for the application needs to take a json string, parse and validate it against various similar but slightly different structures, and then make the values accessible for other bits of downstream processing (e.g. if the file type is a csv file, set some config thus, if it's a json file do this instead); but it's important to note that this is a dynamic process. This seemed to me to be a perfect use case for case classes, but I have a feeling I've misunderstood their use.

So I have a sealed (in order to make sure that all matches are known) abstract class FileConfig, and currently two subclasses, DelimitedConfig and JsonConfig. The DelimitedConfig class also makes use of an additional case class DelimitedFileTypeDetails, which is essentially the main difference between the two at this point, but there will be other deviations added as I continue; and I also have companion objects for all three classes in order to take advantage of the play framework format method:

I am using this code to upload an image on server , that i get from this link play upload

I have created basic Scala Play application with https://www.playframework.com/getting-started play-scala-seed. This project compiles and runs with sbt run. But I have another Scala project that compiles and runs and which I have submitted to my local Ivy repository with command sbt publishLocal. This other project was saved at C:\Users\tomr\.ivy2\local\com.agiintelligence\scala-isabelle_2.13\master-SNAPSHOT as a result of this command.

Then I imported (exactly so - imported, no just opened) my Play project in IntelliJ and I used Project - Open Module Settings - Project Settings - Libraries to add com.agiintelligence jar from my ivy2 location. After such operations IntelliJ editor recognizes com.agiintelligence classes. That is fine.

But when I am trying to run my Play application with sbt run, I experience the error message not found: object com that is exactly when compiling import com.agiintelligence line in my Scala controller file of Play application.

Of course - such error has been reported and resolved with, e.g. object play not found in scala application But that solution suggests to append build.sbt file. My build.sbt file is pretty bare: