Skip to content
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

Jump to bottom

Updates for async api auto config #207

Merged
merged 1 commit into from
Sep 22, 2024
+1 −1
Merged

Updates for async api auto config #207

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
2 changes: 1 addition & 1 deletion _data/snippets/v7/async-api-enable.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Spring: |+2
<br/>
Configure in `application.yaml`.

If you rely on Spring to autodiscover the entities which are placed in the same package/sub-package as the application class with @SpringBootApplication annotation, you will have to add the `@EntityScan` annotation to that application class for those entities to be discovered after async is enabled.
Elide automatically contributes the JPA models for Spring using `@AutoConfigurationPackage` which will be used by Spring automatically if `@EntityScan` is not specified in your application to override auto configuration. However if `@EntityScan` is being used to specify which JPA models to use then the JPA models for the Async API needs to also be explicitly specified for instance `@EntityScan(basePackageClasses = { App.class, AsyncQuery.class })`.

```yaml
elide:
Expand Down