fix for issue 2205 : attribute missing from schema is not handled as expected by replication
When the replication code replay a modify operation on an entry
that contain historical information for an attribute that is
not defined in the schema, the modify operation
is not replayed because an AssertionError is thrown by AttributeValue constructor.
This fixes the problem by avoiding the AssertionError
| | |
| | | attrString = optionsToken[0]; |
| | | } |
| | | else |
| | | { |
| | | attrString = token[0]; |
| | | } |
| | | |
| | | attrType = DirectoryServer.getSchema().getAttributeType(attrString); |
| | | if (attrType == null) |
| | | attrType = DirectoryServer.getDefaultAttributeType(attrString); |
| | | |
| | | cn = new ChangeNumber(token[1]); |
| | | histKey = HistKey.decodeKey(token[2]); |