Customer-developed custom assertions created:
- prior to version 7.1 may fail to load after upgrading to version 7.1
- on version 7.1 may fail to load after upgrading to version 8.0 or later
This is due to a change in the Custom Assertion SDK that causes an “Unknown assertion: CustomAssertion” error to occur.
Specifically, it is not safe to include serialized versions of Layer 7 API classes within your own custom assertion classes. If you do so, your custom assertion may not work on future versions of the Gateway.
If you have written a custom assertion where the actual assertion (implements CustomAssertion) class contains (directly or indirectly) a non-transient, non-static field with a value that is one of the Layer 7 API classes (such as VariableMetadata or DataType), then your custom assertion may not load on future versions of the Gateway.