Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Eager bindings docs clarification #12896

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mkurz merged 1 commit into from
Feb 18, 2025
Merged

Eager bindings docs clarification #12896

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions ...on/manual/working/javaGuide/main/dependencyinjection/JavaDependencyInjection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,16 @@ Eager singletons can be used to start up a service when an application starts. T

@[eager-guice-module](code/javaguide/di/guice/eager/StartModule.java)

It's important to note that the behavior of eager bindings differs between development and production modes:

1. In development mode (`sbt run`):
* Eager bindings are created when the application starts, but they are not fully initialized until the first request is made to the application.
* This behavior improves development experience by reducing startup time and allowing for quicker code changes.
2. In production mode (`sbt stage`):
* Eager bindings are created and fully initialized immediately when the application starts.
* This ensures that all necessary components are ready before the application begins accepting requests.


### Play libraries

If you're implementing a library for Play, then you probably want it to be DI framework agnostic, so that your library will work out of the box regardless of which DI framework is being used in an application. For this reason, Play provides a lightweight binding API for providing bindings in a DI framework agnostic way.
Expand Down
10 changes: 10 additions & 0 deletions .../manual/working/scalaGuide/main/dependencyinjection/ScalaDependencyInjection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,16 @@ Eager singletons can be used to start up a service when an application starts. T

@[eager-guice-module-startup](code/RuntimeDependencyInjection.scala)

It's important to note that the behavior of eager bindings differs between development and production modes:

1. In development mode (`sbt run`):
* Eager bindings are created when the application starts, but they are not fully initialized until the first request is made to the application.
* This behavior improves development experience by reducing startup time and allowing for quicker code changes.
2. In production mode (`sbt stage`):
* Eager bindings are created and fully initialized immediately when the application starts.
* This ensures that all necessary components are ready before the application begins accepting requests.


### Play libraries

If you're implementing a library for Play, then you probably want it to be DI framework agnostic, so that your library will work out of the box regardless of which DI framework is being used in an application. For this reason, Play provides a lightweight binding API for providing bindings in a DI framework agnostic way.
Expand Down
Loading