<div class="wrapper">
    <jsp:include page="/WEB-INF/view/common/admin/header.jsp"></jsp:include>
    <jsp:include page="/WEB-INF/view/common/admin/sidebar.jsp">
        <jsp:param name="menuCategoryType" value="system"/>
        <jsp:param name="menuType" value="dict"/>
    </jsp:include>
    <main class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">

Das bedeutet, dass anstelle des normalen Prozesses, bei dem Ihre Benutzer Requests an Ihre API senden, **Ihre API** (oder Ihre App) **Requests an deren System** (an deren API, deren App) senden könnte.

Das wird normalerweise als **Web<abbr title="Haken, Einhängepunkt">hook</abbr>** bezeichnet.

## Webhooks-Schritte { #webhooks-steps }

Linux-Container) sind eine sehr **leichtgewichtige** Möglichkeit, Anwendungen einschließlich aller ihrer Abhängigkeiten und erforderlichen Dateien zu verpacken und sie gleichzeitig von anderen Containern (anderen Anwendungen oder Komponenten) im selben System isoliert zu halten.

Linux-Container werden mit demselben Linux-Kernel des Hosts (Maschine, virtuellen Maschine, Cloud-Servers, usw.) ausgeführt. Das bedeutet einfach, dass sie sehr leichtgewichtig sind (im Vergleich zu vollständigen virtuellen...

 */
public class StopwordsService {
    /** The dictionary manager for accessing dictionary files. */
    @Resource
    protected DictionaryManager dictionaryManager;

    /** The Fess configuration for accessing system settings. */
    @Resource
    protected FessConfig fessConfig;

    /**
     * Constructs a new stopwords service.
     */
    public StopwordsService() {
        // do nothing
    }

    /**

 */
public class SynonymService {
    /** The dictionary manager for accessing dictionary files. */
    @Resource
    protected DictionaryManager dictionaryManager;

    /** The Fess configuration for accessing system settings. */
    @Resource
    protected FessConfig fessConfig;

    /**
     * Constructs a new synonym service.
     */
    public SynonymService() {
        // do nothing
    }

    /**

    }

    @Override
    public int available() throws IOException {
        return fileInputStream.available();
    }

    /**
     * Closes this input stream and releases any system resources associated with the stream.
     * @throws IOException if an I/O error occurs.
     */
    @Override
    public void close() throws IOException {
        try {
            fileInputStream.close();

    int writeBytesWireFormat(final byte[] dst, int dstIndex) {
        final int start = dstIndex;

        while (pad-- > 0) {
            dst[dstIndex] = (byte) 0xEE;
            dstIndex++;
        }
        System.arraycopy(b, off, dst, dstIndex, dataLength);
        dstIndex += dataLength;

        return dstIndex - start;
    }

    @Override

/**
 * Unit test for {@link Trans2QueryFSInformation}. The class contains mostly
 * trivial wire-format helpers and a custom {@code toString()} implementation.
 * All tests are pure unit tests – no network or file system access is
 * required.
 */
class Trans2QueryFSInformationTest {

    /** Small helper to create a byte buffer larger than the maximum expected
     *  wire format so that we can observe only the bytes written by a method.

  }

  @Benchmark
  public int collapseFrom(int reps) {
    int result = 0;
    CharMatcher matcher = this.matcher;
    String teststring = this.teststring;
    for (int i = 0; i < reps; i++) {
      result += System.identityHashCode(matcher.collapseFrom(teststring, ' '));
    }
    return result;
  }

  private static String allMatchingChars(BitSet bitSet) {
    char[] result = new char[bitSet.cardinality()];

This means that instead of the normal process of your users sending requests to your API, it's **your API** (or your app) that could **send requests to their system** (to their API, their app).

This is normally called a **webhook**.

## Webhooks steps { #webhooks-steps }