Skip to content

Commit

Permalink
Fix spelling of 'query'
Browse files Browse the repository at this point in the history
  • Loading branch information
@psy-q
psy-q committed Oct 19, 2016
1 parent f105e0b commit 32d2285
Show file tree
Hide file tree
Showing 43 changed files with 69 additions and 69 deletions.
2 changes: 1 addition & 1 deletion model/model-impl/src/test/resources/sync/action/account/group-change.xml
View file
Expand Up @@ -456,7 +456,7 @@
<i:correlation> <!-- Correlation rule is a search query -->
<!-- The clause <c:type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-3#UserType"/>
is implicit in correlation rules -->
<!-- Following search queury will look for users that have "name" equal
<!-- Following search query will look for users that have "name" equal
to the "uid" attribute of the account. Simply speaking, it will look for
match in usernames in the IDM and the resource. -->
<c:equal>
Expand Down
2 changes: 1 addition & 1 deletion model/model-impl/src/test/resources/sync/action/user/existing-user-change.xml
View file
Expand Up @@ -457,7 +457,7 @@
<i:correlation> <!-- Correlation rule is a search query -->
<!-- The clause <c:type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-3#UserType"/>
is implicit in correlation rules -->
<!-- Following search queury will look for users that have "name" equal
<!-- Following search query will look for users that have "name" equal
to the "uid" attribute of the account. Simply speaking, it will look for
match in usernames in the IDM and the resource. -->
<c:equal>
Expand Down
2 changes: 1 addition & 1 deletion model/model-impl/src/test/resources/sync/change-correct.xml
View file
Expand Up @@ -437,7 +437,7 @@
<i:correlation> <!-- Correlation rule is a search query -->
<!-- The clause <c:type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-3#UserType"/> is implicit in
correlation rules -->
<!-- Following search queury will look for users that have "name" equal to the "uid" attribute of the account. Simply
<!-- Following search query will look for users that have "name" equal to the "uid" attribute of the account. Simply
speaking, it will look for match in usernames in the IDM and the resource. -->
<c:equal>
<c:path>.</c:path>
Expand Down
2 changes: 1 addition & 1 deletion model/model-impl/src/test/resources/sync/change-without-object.xml
View file
Expand Up @@ -405,7 +405,7 @@
<i:correlation> <!-- Correlation rule is a search query -->
<!-- The clause <c:type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-3#UserType"/> is implicit in
correlation rules -->
<!-- Following search queury will look for users that have "name" equal to the "uid" attribute of the account. Simply
<!-- Following search query will look for users that have "name" equal to the "uid" attribute of the account. Simply
speaking, it will look for match in usernames in the IDM and the resource. -->
<c:equal>
<c:path>.</c:path>
Expand Down
42 changes: 21 additions & 21 deletions repo/audit-api/src/main/java/com/evolveum/midpoint/audit/api/AuditEventType.java
View file
Expand Up @@ -24,25 +24,25 @@
*
*/
public enum AuditEventType {

GET_OBJECT,

ADD_OBJECT,

MODIFY_OBJECT,

DELETE_OBJECT,

EXECUTE_CHANGES_RAW,

SYNCHRONIZATION,
// ....

/**
* E.g. login
*/
CREATE_SESSION,

/**
* E.g. logout
*/
Expand All @@ -54,28 +54,28 @@ public enum AuditEventType {
WORK_ITEM,

WORKFLOW_PROCESS_INSTANCE,

RECONCILIATION;

/**
* Queury session, modify session
* Query session, modify session
*/

/**
* Task states???
* Task states???
*/

/**
* Startup, shutdown, critical failure (whole system)
*/

// backup, restores

public static AuditEventType toAuditEventType(AuditEventTypeType event){
if (event == null){
return null;
}

switch (event){
case ADD_OBJECT:
return AuditEventType.ADD_OBJECT;
Expand All @@ -101,16 +101,16 @@ public static AuditEventType toAuditEventType(AuditEventTypeType event){
return AuditEventType.WORKFLOW_PROCESS_INSTANCE;
default:
throw new IllegalArgumentException("Unknown audit event type: " + event);

}

}

public static AuditEventTypeType fromAuditEventType(AuditEventType event){
if (event == null){
return null;
}

switch (event){
case ADD_OBJECT:
return AuditEventTypeType.ADD_OBJECT;
Expand All @@ -136,9 +136,9 @@ public static AuditEventTypeType fromAuditEventType(AuditEventType event){
return AuditEventTypeType.WORKFLOW_PROCESS_INSTANCE;
default:
throw new IllegalArgumentException("Unknown audit event type: " + event);

}

}

}
2 changes: 1 addition & 1 deletion repo/repo-sql-impl-test/src/test/resources/basic/objects.xml
View file
Expand Up @@ -540,7 +540,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion repo/repo-sql-impl-test/src/test/resources/modify/resource-csv.xml
View file
Expand Up @@ -239,7 +239,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion repo/repo-sql-impl-test/src/test/resources/modify/resource-opendj.xml
View file
Expand Up @@ -466,7 +466,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/demo-generic synchronization/resource-GenSync-OpenDJ.xml
View file
Expand Up @@ -13431,7 +13431,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/demo-rs/resource-csv-source.xml
View file
Expand Up @@ -210,7 +210,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/demo-rs/resource-csv-xxx.xml
View file
Expand Up @@ -237,7 +237,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/demo-rs/resource-ldap-openldap.xml
View file
Expand Up @@ -498,7 +498,7 @@ It also contains inbound mappings and definition to enable synchronization.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/demo/hr.xml
View file
Expand Up @@ -185,7 +185,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
4 changes: 2 additions & 2 deletions samples/demo/opendj.xml
View file
Expand Up @@ -469,7 +469,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down Expand Up @@ -523,7 +523,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
4 changes: 2 additions & 2 deletions samples/demo/openldap.xml
View file
Expand Up @@ -444,7 +444,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down Expand Up @@ -498,7 +498,7 @@
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/389ds/389ds-legacy-connector.xml
View file
Expand Up @@ -392,7 +392,7 @@ It also contains inbound mappings and definition to enable synchronization.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/ad/ad-resource-advanced-sync.xml
View file
Expand Up @@ -316,7 +316,7 @@ to "false". The only way of resetting the flag is to change user's password.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "sAMAccountName" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/csvfile/localhost-csvfile-medium.xml
View file
Expand Up @@ -191,7 +191,7 @@ using an Identity Connector Framework connector.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/csvfile/localhost-csvfile-resource-advanced-sync-2.xml
View file
Expand Up @@ -221,7 +221,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/csvfile/localhost-csvfile-resource-advanced-sync.xml
View file
Expand Up @@ -221,7 +221,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/csvfile/localhost-csvfile-resource-bulk-action.xml
View file
Expand Up @@ -221,7 +221,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "name" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/dsee/odsee-localhost-advanced-nosync.xml
View file
Expand Up @@ -319,7 +319,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/office365/office365-federated.xml
View file
Expand Up @@ -285,7 +285,7 @@ This contains configuration for a federated Office 365 domain
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "mailNickname" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/office365/office365-managed.xml
View file
Expand Up @@ -265,7 +265,7 @@ This contains configuration for a managed (non federated) Office 365 domain
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "mailNickname" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/opendj/opendj-localhost-medium.xml
View file
Expand Up @@ -339,7 +339,7 @@ It also contains inbound mappings and definition to enable synchronization.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/opendj/opendj-localhost-resource-sync-advanced.xml
View file
Expand Up @@ -375,7 +375,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/opendj/opendj-localhost-resource-sync-no-extension-advanced-test.xml
View file
Expand Up @@ -385,7 +385,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/opendj/opendj-localhost-resource-sync-no-extension-advanced.xml
View file
Expand Up @@ -383,7 +383,7 @@ object.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/opendj/piracy/opendj-localhost-resource-sync-extension-pirates.xml
View file
Expand Up @@ -452,7 +452,7 @@ This resource definition contains also definition to enable synchronization.
<correlation>
<!-- Correlation rule is a search query -->
<!-- The clause <type uri="http://midpoint.evolveum.com/xml/ns/public/common/common-3#UserType"/> is implicit in correlation rules -->
<!-- Following search queury will look for users that have "name"
<!-- Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource. -->
<q:equal>
Expand Down
2 changes: 1 addition & 1 deletion samples/resources/openldap/openldap-localhost-medium.xml
View file
Expand Up @@ -425,7 +425,7 @@ It also contains inbound mappings and definition to enable synchronization.
<correlation>
<q:description>
Correlation expression is a search query.
Following search queury will look for users that have "name"
Following search query will look for users that have "name"
equal to the "uid" attribute of the account. Simply speaking,
it will look for match in usernames in the IDM and the resource.
The correlation rule always looks for users, so it will not match
Expand Down

0 comments on commit 32d2285

Please sign in to comment.