Skip to content
This repository has been archived by the owner on Mar 11, 2022. It is now read-only.

Classpath scanners performance #3

Open
sleipnir opened this issue Mar 28, 2020 · 1 comment
Open

Classpath scanners performance #3

sleipnir opened this issue Mar 28, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@sleipnir
Copy link

While cloudstate java support does not allow better interaction with injection containers, we will need to improve our ability to identify the entity classes annotated with @EventSourcedEntity and CrdtEntity.

We can, via configuration, indicate what types of entities are needed within the context of execution so that we go through the classpath only as much as necessary

@sleipnir sleipnir added enhancement New feature or request good first issue Good for newcomers labels Mar 28, 2020
@sleipnir sleipnir self-assigned this Mar 28, 2020
@sleipnir
Copy link
Author

sleipnir commented Apr 3, 2020

We added the possibility for the customer to define the name of the package that his entity role was created. This way we can use Spring's available resources to scan classes instead of using the classgraph library, thereby reducing the application load time by more than one second on average.
In the future we will be able to remove the dependency of the classgraph entirely. But first we need to receive more feedback from the community

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant