NullValidator should not contain allowNull

[Mauno Haukila]

It makes no sence for NullValidator? to have allowNull option. Who would really create this validator: new NullValidator?("this warning is never shown", true);

[Joonas Lehtinen]

The idea with AllowNull? property has been:

• if true, then non-nulls are not allowed.
• If false, only non-null:s are allowed.

This way it makes sense.

Another question is if it has been implemented correctly.... (we should check before closing this ticket). Moving to 5.1.

[Mauno Haukila]

If someone would require component where only null is allowed he/she would most probably make it null&read-only.

I'm pretty sure that if someone would REALLY require "allow-null-only" functionality he/she wouldn't find NullValidator for the purpose because of it's documentation and api.

* This validator is used for validating properties that do or do not allow null
 * values. By default, nulls are not allowed.
 *

and constructor:

/**
     * Creates a new NullValidator.
     *
     * @param errorMessage
     *                the error message to display on invalidation.
     * @param allowNull
     *                Are nulls allowed?
     */
    public NullValidator(String errorMessage, boolean allowNull) {

[Marc Englund]

This is a documentation issue: allowNull actually means requireNull. If it makes sense or is useful is another question...

[Joonas Lehtinen]

Milestone Sprint 4 backlog deleted

[Joonas Lehtinen]

Milestone User Interface Library 5.1.2 deleted

[Marc Englund]

Fixed in #4444 (allowNull is now onlyNullAllowed)