Class Resource

java.lang.Object
com.evolveum.midpoint.schema.util.Resource

@Experimental public class Resource extends Object
"One stop shop" for accessing various aspects of a resource (defined by ResourceType object). Currently used for: - accessing the schema, - creating queries. Resides as low as in `schema` module, because it is used also in AbstractIntegrationTest class. This limits the functionality provided, though. Open questions: - Should we change the name to reflect that it is more schema-oriented? - Should we merge this class e.g. with ResourceSchema? Or ResourceTypeUtil? - Should we add more functionality here and move back to `provisioning-api`? HIGHLY EXPERIMENTAL (maybe not a good idea at all)