*
 */
public class AdminSearchlogAction extends FessAdminAction {

    /**
     * Default constructor.
     */
    public AdminSearchlogAction() {
        super();
    }

    /** Role name for admin search log operations */
    public static final String ROLE = "admin-searchlog";

    private static final String[] CONDITION_FIELDS =

            result.setCreatedTime(DfTypeUtil.toLong(source.get("createdTime")));
            result.setExpiredTime(DfTypeUtil.toLong(source.get("expiredTime")));
            result.setName(DfTypeUtil.toString(source.get("name")));
            result.setParameterName(DfTypeUtil.toString(source.get("parameter_name")));
            result.setPermissions(toStringArray(source.get("permissions")));

        try {
            final RESULT result = entityType.newInstance();
            result.setGidNumber(DfTypeUtil.toLong(source.get("gidNumber")));
            result.setName(DfTypeUtil.toString(source.get("name")));
            return updateEntity(source, result);
        } catch (InstantiationException | IllegalAccessException e) {
            final String msg = "Cannot create a new instance: " + entityType.getName();

        // Both instances should be of the same class
        assertEquals(exception1.getClass(), exception2.getClass());

        // Test serialization compatibility by checking class name
        assertEquals("org.codelibs.fess.exception.CommandExecutionException", exception1.getClass().getName());
    }

    @Test
    public void test_exceptionThrown() {

    response.use {
      assertEquals(200, response.code)
      assertEquals(
        "CN=localhost",
        (response.handshake!!.peerCertificates.single() as X509Certificate).subjectDN.name,
      )
    }
  }

  private fun enableTls() {
    client =
      client
        .newBuilder()
        .sslSocketFactory(
          handshakeCertificates.sslSocketFactory(),

name: Feature Addition Request
description: I want to add a new feature
labels: ["type=addition"]
body:
  - type: markdown
    attributes:
      value: >
        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our

        // Assertions
        // readBytesWireFormat returns bytes processed up to null terminator
        assertEquals(14, bytesRead); // 8 bytes key + 6 bytes domain name
        assertArrayEquals(encryptionKey, serverData.encryptionKey);
        assertEquals("DOMAIN", serverData.oemDomainName);
    }

    @Test

因此，同一個模型的 JSON Schema 會依用於輸入或輸出而不同：

- 用於輸入時，`description` 不是必填
- 用於輸出時，`description` 是必填（且可能為 `None`，在 JSON 中為 `null`）

### 文件中的輸出模型 { #model-for-output-in-docs }

你也可以在文件中檢視輸出模型，`name` 與 `description` 都以紅色星號標示為必填：

<div class="screenshot">
<img src="/img/tutorial/separate-openapi-schemas/image03.png">
</div>

### 文件中的輸入與輸出模型 { #model-for-input-and-output-in-docs }

因此，一个模型的 JSON Schema 会根据它用于**输入还是输出**而有所不同：

- 用于**输入**时，`description` **不是必填**
- 用于**输出**时，它是**必填**（并且可能为 `None`，在 JSON 中为 `null`）

### 文档中的输出模型 { #model-for-output-in-docs }

你也可以在文档中查看输出模型，`name` 和 `description` **都**被**红色星号**标记为**必填**：

<div class="screenshot">
<img src="/img/tutorial/separate-openapi-schemas/image03.png">
</div>

### 文档中的输入/输出模型 { #model-for-input-and-output-in-docs }

All container images are available as manifest lists and support the described
architectures. It is also possible to pull a specific architecture directly by
adding the "-$ARCH" suffix  to the container image name.

name | architectures
---- | -------------