proporcionado no es válido",wrongFileDim:"Las dimensiones de la imagen no son validas,",imageTooTall:"el alto de la imagen no puede ser mayor a",imageTooWide:"el ancho de la imagen no puede ser mayor a",imageTooSmall:"la imagen es demasiado pequeña",min:"min.",max:"máx.",imageRatioNotAccepted:"La proporción de imagen (alto x ancho) no es válida",passwordComplexityStart:"La contraseña debe contener al menos ",passwordComplexitySeparator:", ",passwordComplexityUppercaseInfo:" mayúscula(s)",passwordCom...

////

Agora o cliente irá receber a mesma resposta *HTTP 500 Internal Server Error*, mas o servidor terá nosso `InternalError` personalizado nos logs. 😎

## Execução de dependências com `yield`

A sequência de execução é mais ou menos como esse diagrama. O tempo passa do topo para baixo. E cada coluna é uma das partes interagindo ou executando código.

```mermaid
sequenceDiagram

participant client as Cliente

"validatorsLoaded",function(){a.formUtils.LANG={errorTitle:"Ошибка отправки формы!",requiredField:"Это обязательное поле",requiredFields:"Вы задали не все обязательные поля",badTime:"Вы задали некорректное время",badEmail:"Вы задали некорректный e-mail",badTelephone:"Вы задали некорректный номер телефона",badSecurityAnswer:"Вы задали некорректный ответ на секретный вопрос",badDate:"Вы задали некорректную дату",lengthBadStart:"Значение должно быть в диапазоне",lengthBadEnd:" символов",lengthTooLongStart:"Значение...

 Mas quando o formulário inclui arquivos, ele é codificado como `multipart/form-data`. Você lerá sobre como lidar com arquivos no próximo capítulo.

    /**
     * Get the value for the key 'mail.hostname'. <br>
     * The value is, e.g.  <br>
     * comment: Hostname for the mail server.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getMailHostname();

    /**
     * Get the value for the key 'mail.hostname' as {@link Integer}. <br>
     * The value is, e.g.  <br>

constraints.Min.message = {item} must be greater than or equal to {value}.
constraints.NotNull.message = {item} is required.
constraints.Null.message = {item} must be null.
constraints.Past.message = {item} must be a past value.
constraints.Pattern.message = {item} does not match "{regexp}".
constraints.Size.message = The size of {item} must be between {min} and {max}.

constraints.Min.message = {item} must be greater than or equal to {value}.
constraints.NotNull.message = {item} is required.
constraints.Null.message = {item} must be null.
constraints.Past.message = {item} must be a past value.
constraints.Pattern.message = {item} does not match "{regexp}".
constraints.Size.message = The size of {item} must be between {min} and {max}.

 */
package org.codelibs.fess.app.web.admin.general;

import org.lastaflute.web.validation.Required;

import jakarta.validation.constraints.Size;

/**
 * The mail form for General settings.
 */
public class MailForm {

    /**
     * Default constructor.
     */
    public MailForm() {
        // Default constructor
    }

     * implementations, supports add() under JDK8. This seems problematic, but I
     * didn't see that discussed in the review, which included many other
     * changes: https://mail.openjdk.org/pipermail/core-libs-dev/2013-May/thread.html#17367
     *
     * TODO(cpovirk): decide what the best long-term action here is: force users
     * to suppress (as we do now), stop testing entrySet().add() at all, make

labels.user_given_name=Vorname
labels.givenName=Vorname (gegebener Name)
labels.user_surname=Nachname
labels.surame=Nachname
labels.user_mail=E-Mail
labels.mail=E-Mail
labels.user_employeeNumber=Mitarbeiternummer
labels.employeeNumber=Mitarbeiternummer
labels.user_telephoneNumber=Telefonnummer
labels.telephoneNumber=Telefonnummer
labels.user_homePhone=Telefon (privat)