If there is an invalid attribute in the filter (for
example, one for which Schema Mapping is not defined), the following
happens:
- At each polling loop, the Publisher
fails to synchronize the class that contains the invalid attribute,
and gives an error indicating an unsupported attribute.
- The driver is still able to start.
- The Subscriber channel still functions correctly
unless the invalid attribute is referenced. A task that references
an invalid attribute gives an error and is not successful.
The sample driver configuration supports the standard attributes
in Exchange, so this issue could occur only for custom attributes
you have added in Exchange.