ProcessingScope.PostSearchFilterImpl (midPoint Aggregate JavaDoc)

java.lang.Object
- com.evolveum.midpoint.model.impl.sync.tasks.ProcessingScope.PostSearchFilterImpl

All Implemented Interfaces:

PostSearchFilter

Enclosing class:

ProcessingScope
```
@Experimental
public class ProcessingScope.PostSearchFilterImpl
extends Object
implements PostSearchFilter
```
Specifies which objects are to be synchronized. Currently uses combination of object class, kind, and intent. (No custom filters yet.) TODO shouldn't we take object class inheritance (subtyping) into account?

- Constructor Summary
  
  Constructors
  Constructor Description
  
  PostSearchFilterImpl()
- Method Summary
  
  All Methods Instance Methods Concrete Methods
  Modifier and Type Method Description
  
  boolean matches(@NotNull PrismObject<ShadowType> shadow)
  - Methods inherited from class java.lang.Object
    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - PostSearchFilterImpl
```
public PostSearchFilterImpl()
```
- Method Detail
  - matches
```
public boolean matches(@NotNull
                       @NotNull PrismObject<ShadowType> shadow)
```
    Specified by:
    
    matches in interface PostSearchFilter
    
    Returns:
    
    True if we should process given shadow in this synchronization task. (Normally, we check object class, kind, and intent with regards to values provided by the task.)