if (labelTypeHelper != null) {
            labelTypeHelper.refresh(getLabelTypeList());
        }
    }

    /**
     * Get a label type.
     *
     * @param id The ID of the label type.
     * @return An optional entity of the label type.
     */
    public OptionalEntity<LabelType> getLabelType(final String id) {
        return labelTypeBhv.selectByPK(id);
    }

        feature and its potential value for other Guava users.

  - type: textarea
    attributes:
      label: 1. What are you trying to do?
    validations:
      required: true

  - type: textarea
    attributes:
      label: 2. What's the best code you can write to accomplish that without the new feature?
    validations:
      required: true

  - type: textarea
    attributes:

    validations:
      required: true
  - type: dropdown
    id: os
    attributes:
      label: Operating System
      description: What operating system are you on?
      multiple: true
      options:
        - Linux
        - Windows
        - macOS
        - Other
    validations:
      required: true
  - type: textarea
    id: os-details
    attributes:

      |Content-Type: multipart/mixed; boundary=BbC04y
      |
      |--BbC04y
      |Content-Disposition: file; filename="file1.txt"
      |Content-Type: text/plain; charset=utf-8
      |
      |... contents of file1.txt ...
      |--BbC04y
      |Content-Disposition: file; filename="file2.gif"
      |Content-Transfer-Encoding: binary
      |Content-Type: image/gif
      |

diretamente (ou qualquer subclasse, como `JSONResponse`), os dados não serão convertidos automaticamente (mesmo que você declare um `response_model`), e a documentação não será gerada automaticamente (por exemplo, incluindo o "media type", no cabeçalho HTTP `Content-Type` como parte do esquema OpenAPI gerado).

Mas você também pode declarar a `Response` que você deseja utilizar (e.g. qualquer subclasse de `Response`), em um *decorador de operação de rota* utilizando o parâmetro `response_class`....

    }

    @Override
    public NbtAddress getNbtByName(final String host, final int type, final String scope) throws UnknownHostException {
        return getNbtByName(host, type, scope, null);
    }

    @Override
    public NbtAddress getNbtByName(final String host, final int type, final String scope, final InetAddress svr)
            throws UnknownHostException {

     */
    void updateType(final int t) {
        this.type = t;
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.SmbResourceLocator#getType()
     */
    @Override
    public int getType() throws CIFSException {
        if (this.type == 0) {
            if (getUNCPath().length() > 1) {
                this.type = SmbConstants.TYPE_FILESYSTEM;
            } else if (getShare() != null) {

    /**
     * Get the numeric value of this handle type
     * @return the numeric value
     */
    public int getValue() {
        return value;
    }

    /**
     * Get HandleType from numeric value
     * @param value the numeric value
     * @return the corresponding HandleType
     */
    public static HandleType fromValue(int value) {
        for (HandleType type : values()) {
            if (type.value == value) {

 *
 * <h3>For Java 8+ users</h3>
 *
 * <p>This interface is now a legacy type. Use {@code java.util.function.Supplier} (or the
 * appropriate primitive specialization such as {@code IntSupplier}) instead whenever possible.
 * Otherwise, at least reduce <i>explicit</i> dependencies on this type by using lambda expressions
 * or method references instead of classes, leaving your code easier to migrate in the future.
 *

   | way you don't have to hardcode paths in your pom.xml.
   |
   | Every toolchain consist of 3 elements:
   | * type: the type of tool. An often used value is 'jdk'. Toolchains-aware
   |   plugins should document which type you must use.
   |
   | * provides: A list of key/value-pairs.
   |   Based on the toolchain-configuration in the pom.xml Maven will search for