What is the difference between a dependency router and a static router in ScalaRouting from the Play Framework?

Question

What is the difference between a dependency-embedded router and a static router in ScalaRouting for a playback platform?

The documentation for the framework documentation directly depends on the nested router used when creating the new Play application using the templates of the playback initiator.

But I'm still confused on both routers.

If anyone knows, please teach me.

Answer 1

In a nutshell

. . . , .

. Play 2.0 ( Java) ( Scala). , MVC , , . , , unit test, . .

Play 2.1 , . , @ .

2.4 getControllerInstance() , 2.4 .

, - , , , .