Таким же образом вы можете поднять исключение `HTTPException` или что-то подобное в завершающем коде, после `yield`.

Код выхода в зависимостях с `yield` выполняется *после* отправки ответа, поэтому [Обработчик исключений](../handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} уже будет запущен. В коде выхода (после `yield`) нет ничего, перехватывающего исключения, брошенные вашими зависимостями.

import org.codelibs.fess.app.web.admin.elevateword.DownloadForm;

/**
 * Download body for elevate word API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading elevate word configurations via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */
    public DownloadBody() {

package org.codelibs.fess.app.web.api.admin.badword;

import org.codelibs.fess.app.web.admin.badword.DownloadForm;

/**
 * Download body for Bad Word API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading bad word dictionaries via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */
    public DownloadBody() {
        super();

import org.codelibs.fess.crawler.entity.ResponseData;

/**
 * The ResponseProcessor interface defines a contract for processing response data.
 * Implementations of this interface are responsible for handling the response data
 * obtained during a crawling process.
 */
public interface ResponseProcessor {

    /**
     * Processes the given response data.
     *

                "Command should change to SMB_COM_TRANSACTION_SECONDARY");
    }

    @Test
    @DisplayName("Test NT transaction command handling")
    void testNtTransactionCommand() {
        transaction.command = ServerMessageBlock.SMB_COM_NT_TRANSACT;

        // First call
        transaction.nextElement();

# Security { #security }

There are many ways to handle security, authentication and authorization.

And it normally is a complex and "difficult" topic.

In many frameworks and systems just handling security and authentication takes a big amount of effort and code (in many cases it can be 50% or more of all the code written).

import org.codelibs.fess.app.web.admin.dict.kuromoji.DownloadForm;

/**
 * Download body for Kuromoji dictionary API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading Kuromoji dictionaries via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */
    public DownloadBody() {
        super();

import org.codelibs.fess.app.web.admin.dict.protwords.DownloadForm;

/**
 * Download body for protected words dictionary API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading protected words dictionaries via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */
    public DownloadBody() {

import org.codelibs.fess.app.web.admin.dict.stopwords.DownloadForm;

/**
 * Download body for stop words dictionary API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading stop words dictionaries via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */
    public DownloadBody() {
        super();

   * a robolectric test.
   *
   * The functionality that will fail without a valid Context is primarily Cookies and URL Domain handling, but
   * may expand in the future.
   */
  fun initialize(applicationContext: Context) {
    if (PlatformRegistry.applicationContext == null) {
      // Make sure we aren't using an Activity or Service Context