-
Notifications
You must be signed in to change notification settings - Fork 188
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Support native midPoint associations
The main goal of this commit is to support native midPoint associations. They were added into ConnId in 652bf46b0b8625817ce6a67634b592b217f65842; their support into prism in 12808dc91f4ea358dda3666cd0b01eba7d08300c. Main change: Instead of ResourceSchema that somehow contained both raw and refined (native and complete, in more modern terms) definitions, now we have the following structures: - NativeResourceSchema and its components: NativeObjectClassDefinition, NativeShadowItemDefinition (with subtypes for attributes and associations), and very experimental NativeAssociationClassDefinition. They contain information obtained from the connector or specified manually via XSD; and nothing more. These are not even prism definitions. - ResourceSchema and its components (as before): ResourceObjectDefinition (for both object classes and object types), ShadowItemDefinition (for attributes and associations), and so on. These can be used in midPoint as they are regular prism definitions. Note that CompleteResourceSchema contains the full information known from ResourceType; whereas BareResourceSchema is the old "raw" one, that is suitable mainly for testing and diagnostics. The CompleteResourceSchema should be used in the code. Maybe we'll find a better name in the future. Only the native definitions can be transformed into XSD. Only the adopted ones (ResourceSchema) can be meaningfully used in midPoint. Other changes: 1. The background change in prism was quite massive. Many places in midPoint code had to be adapted to it. 2. (Unrelated change) ConnectorSchema was revived, and is used to store connector configuration schemas. Creation and use of these objects was simplified. Please use it (instead of PrismSchema) for connectors. 3. Subject-bound association definition style is back, at least for now. 4. Removed support for obsolete ref-style schema annotations like <r:identifier ref="icfs:uid"/>. They weren't used since 2.0. 5. Dropped support for a:documentation for manually-entered resource XSD schemas (ConnId does not support that anyway). But this is to be reconsidered. Work in progress.
- Loading branch information
Showing
346 changed files
with
9,122 additions
and
7,926 deletions.
There are no files selected for viewing
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
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
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
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.