#### Docker Compose { #docker-compose }

Sie könnten das Deployment auf einem **einzelnen Server** (kein Cluster) mit **Docker Compose** durchführen, sodass Sie keine einfache Möglichkeit hätten, die Replikation von Containern (mit Docker Compose) zu verwalten und gleichzeitig das gemeinsame Netzwerk mit **Load Balancing** zu haben.

    * Composite bodies' IDs are now based on path, not only on route name, as the auto-generated name uses the function names, that can be duplicated in different modules.
    * The same new ID generation applies to response models.
    * This also changes the generated title for those models.

# Test Guide

```bash
cd tests
# prepare test databases
docker-compose up

# run all tests
./tests_all.sh

#### Docker Compose { #docker-compose }

You could be deploying to a **single server** (not a cluster) with **Docker Compose**, so you wouldn't have an easy way to manage replication of containers (with Docker Compose) while preserving the shared network and **load balancing**.

#### Docker Compose { #docker-compose }

Podrías estar desplegando en un **servidor único** (no un cluster) con **Docker Compose**, por lo que no tendrías una forma fácil de gestionar la replicación de contenedores (con Docker Compose) mientras se preserva la red compartida y el **load balancing**.

    <default>
      <key>package</key>
      <value>org.apache.maven.plugin.resources.remote</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="supplementalDataModels" xsd.compositor="sequence">
      <name>SupplementalDataModel</name>
      <version>1.0.0</version>
      <description>Root element of the supplemental-models.xml file.</description>
      <fields>
        <field xml.listStyle="flat">

          @Override
          public boolean removeAll(Collection<?> c) {
            return removeEntryIf(compose(in(c), Entry::getValue));
          }

          @Override
          public boolean retainAll(Collection<?> c) {
            return removeEntryIf(compose(not(in(c)), Entry::getValue));
          }
        };
      }
    }
  }

  @Override

    Predicate<String> trimEqualsFoo = Predicates.compose(equalsFoo, trim);
    Function<String, String> identity = Functions.identity();

    assertTrue(trimEqualsFoo.apply("Foo"));
    assertTrue(trimEqualsFoo.apply("   Foo   "));
    assertFalse(trimEqualsFoo.apply("Foo-b-que"));

    new EqualsTester()
        .addEqualityGroup(trimEqualsFoo, Predicates.compose(equalsFoo, trim))
        .addEqualityGroup(equalsFoo)

#### Docker Compose { #docker-compose }

Você pode estar implantando em um **único servidor** (não em um cluster) com o **Docker Compose**, então você não teria uma maneira fácil de gerenciar a replicação de contêineres (com o Docker Compose) enquanto preserva a rede compartilhada e o **balanceamento de carga**.

import org.apache.maven.api.annotations.Immutable;

import static org.apache.maven.api.ExtensibleEnums.projectScope;

/**
 * Project scope.
 * Defines the type of source files to compile, usually either the one that compose the output package
 * (i.e. the <i>main</i> artifact) or the ones that will be used when building <i>tests</i>).
 * <p>
 * This extensible enum has two defined values, {@link #MAIN} and {@link #TEST},