Package org.forgerock.opendj.ldap

Class ConstraintViolationException

  • All Implemented Interfaces:
    Serializable, LocalizableException
    public final class ConstraintViolationException
extends LdapException
    Thrown when the result code returned in a Result indicates that the update Request failed because it would have left the Directory in an inconsistent state. More specifically, this exception is used for the following error result codes:
    • ATTRIBUTE_OR_VALUE_EXISTS - the Request failed because it would have resulted in a conflict with an existing attribute or attribute value in the target entry.
    • NO_SUCH_ATTRIBUTE - the Request failed because it targeted an attribute or attribute value that did not exist in the specified entry.
    • CONSTRAINT_VIOLATION - the Request failed because it would have violated some constraint defined in the server.
    • ENTRY_ALREADY_EXISTS - the Request failed because it would have resulted in an entry that conflicts with an entry that already exists.
    • INVALID_ATTRIBUTE_SYNTAX - the Request failed because it violated the syntax for a specified attribute.
    • INVALID_DN_SYNTAX - the Request failed because it would have resulted in an entry with an invalid or malformed DN.
    • NAMING_VIOLATION - the Request failed becauseit would have violated the server's naming configuration.
    • NOT_ALLOWED_ON_NONLEAF - the Request failed because it is not allowed for non-leaf entries.
    • NOT_ALLOWED_ON_RDN - the Request failed because it is not allowed on an RDN attribute.
    • OBJECTCLASS_MODS_PROHIBITED - the Request failed because it would have modified the objectclasses associated with an entry in an illegal manner.
    • OBJECTCLASS_VIOLATION - the Request failed because it would have resulted in an entry that violated the server schema.
    • UNDEFINED_ATTRIBUTE_TYPE - the Request failed because it referenced an attribute that is not defined in the server schema.
    See Also:
    Serialized Form