Play Framework 3.(0.5) Java and Pac4J [cross-posting] #12867
-
Dear Community, I first posted this on but the error message seem to be based on a change in Play Framework (3 Java). I am using Pac4J Security library and the recent demo application release does not run / compile on my JDK 17, Linux environment, Pekko engine).
2.9.5 works with pac4j-play, but complains that it is missing the jakarta.x.validation class (documented in the migration guide though). The problem should be reproducible by compiling the demo app from github. Any help/feedback is appreciated. Thanks in advance. Henning |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I am not sure why this is not working. First, the demo uses Scala 3.5 which Play does not support, so I downgraded to Scala 3.3.4 LTS but still the error occurs (also tried with 3.3.3 btw.). Maybe the library is compiled with a newer version of Scala therefore is incompatible with Play's artifacts? Not sure. Meanwhile, because you try to use Play Java anyway, what you can do is just use Scala 2.13, this does actually work - see mkurz/play-pac4j-java-demo@121ede6 I will create an issue out of this thread so it gets tracked and a deeper look will be take what really is going on with Scala 3 here. |
Beta Was this translation helpful? Give feedback.
I am not sure why this is not working. First, the demo uses Scala 3.5 which Play does not support, so I downgraded to Scala 3.3.4 LTS but still the error occurs (also tried with 3.3.3 btw.). Maybe the library is compiled with a newer version of Scala therefore is incompatible with Play's artifacts? Not sure.
Meanwhile, because you try to use Play Java anyway, what you can do is just use Scala 2.13, this does actually work - see mkurz/play-pac4j-java-demo@121ede6
For you in the end it does not matter if you are using Scala 3 or 2 under the hood.
I will create an issue out of this thread so it gets tracked and a deeper look will be take what really is going on with Scala 3 here.