Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve applySchemasAndSecurity perf test
The test is now more realistic, as there's an archetype plus template with some definition overriding. Moreover, we introduced three modes of definition updating: NONE, ROOT_ONLY, and FULL. The first two would allow use pre-computed definitions for archetypes without the need to touch the objects (except for cloning immutable ones!). Hence, we'll aim for NONE definition update mode, if possible.
- Loading branch information
Showing
8 changed files
with
323 additions
and
68 deletions.
There are no files selected for viewing
39 changes: 39 additions & 0 deletions
39
infra/schema/src/main/java/com/evolveum/midpoint/schema/DefinitionUpdateOption.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
/* | ||
* Copyright (c) 2010-2017 Evolveum and contributors | ||
* | ||
* This work is dual-licensed under the Apache License 2.0 | ||
* and European Union Public License. See LICENSE file for details. | ||
*/ | ||
|
||
package com.evolveum.midpoint.schema; | ||
|
||
import com.evolveum.midpoint.util.annotation.Experimental; | ||
|
||
/** | ||
* Should be definitions updated after an object is retrieved via model API? | ||
* See `applySchemasAndSecurity` method. | ||
* | ||
* Applicable only on the root level. | ||
* | ||
* TEMPORARY, mainly for the purposes of experiments with various approaches during midPoint 4.8 development. | ||
*/ | ||
@Experimental | ||
public enum DefinitionUpdateOption { | ||
|
||
/** | ||
* The object or container definition is not to be updated at all. | ||
*/ | ||
NONE, | ||
|
||
/** | ||
* Only the definition at the root level (object or container) is updated. | ||
* Definitions of the child items (if any) are not touched. | ||
* For example, the client may apply the root definition if needed. | ||
*/ | ||
ROOT_ONLY, | ||
|
||
/** | ||
* Updated definition is propagated onto all items in the returned structure. | ||
*/ | ||
DEEP; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.