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.

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

Whitelisting audited classes & properties #616

bartoszwalacik opened this Issue Dec 5, 2017 · 1 comment


None yet
1 participant

bartoszwalacik commented Dec 5, 2017

In JaVers all objects and their properties are audited by default. There are various ways to ignore some of them.
This approach becomes hard when a user wants to audit only a small fraction of his data.

Opposite or mixed approach can be developed to give more control over type mapping process to JaVers user. Since we don't want to add more annotations to JaVers, the solution would be based on filters.

There are two API changes that we need:

/** Hook here to change a ClientsClassDefinition produced by ClassScanner */
interface ClientsClassDefinitionFilter {
    ClientsClassDefinition applyFilter(ClientsClassDefinition source);

bartoszwalacik added a commit that referenced this issue Jan 14, 2018

stefanicai added a commit that referenced this issue Jan 23, 2018

#616: Added DifInclude annotation and updated code to take that into …
…account when generating ManagedClass for a specific type/class

stefanicai added a commit that referenced this issue Jan 23, 2018

#616: fixed issue with conversion from String[] to Set<String>. Added…
… test for ClassAnnotationsScanner when scanned class is annotated with DiffInclude

@bartoszwalacik bartoszwalacik added the fixed label Feb 6, 2018


This comment has been minimized.


bartoszwalacik commented Feb 6, 2018

property-level @DiffIndlude released in 3.8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment