the add-opens. Right now that doesn't seem worth the effort, though.
    -->
    <test.add.opens>
      --add-opens java.base/java.lang=ALL-UNNAMED
      --add-opens java.base/java.util=ALL-UNNAMED
      --add-opens java.base/sun.security.jca=ALL-UNNAMED
    </test.add.opens>
    <module.status>integration</module.status>

    the add-opens. Right now that doesn't seem worth the effort, though.
    -->
    <test.add.opens>
      --add-opens java.base/java.lang=ALL-UNNAMED
      --add-opens java.base/java.util=ALL-UNNAMED
      --add-opens java.base/sun.security.jca=ALL-UNNAMED
    </test.add.opens>
    <module.status>integration</module.status>

    /**
     * Opens the file for random access
     *
     * @param mode
     *            access mode (r|rw)
     * @return random access file, needs to be closed when finished
     * @throws CIFSException if an error occurs accessing the resource
     */
    SmbRandomAccess openRandomAccess(String mode) throws CIFSException;

    /**

    public static final int SMB2_IMPERSONATION_LEVEL_DELEGATE = 0x3;

    /**
     * Enable other opens for read access
     */
    public static final int FILE_SHARE_READ = 0x1;

    /**
     * Enable other opens for write access
     */
    public static final int FILE_SHARE_WRITE = 0x2;

    /**
     * Enable other opens for delete access
     */
    public static final int FILE_SHARE_DELETE = 0x4;

    /**

### Cache the OpenAPI schema { #cache-the-openapi-schema }

You can use the property `.openapi_schema` as a "cache", to store your generated schema.

That way, your application won't have to generate the schema every time a user opens your API docs.

It will be generated only once, and then the same cached schema will be used for the next requests.

{* ../../docs_src/extending_openapi/tutorial001.py hl[13:14,25:26] *}

    /**
     * Share flag indicating the share is a DFS root.
     */
    public static final int SMB2_SHAREFLAG_DFS_ROOT = 0x2;
    /**
     * Share flag indicating that exclusive opens are restricted on this share.
     */
    public static final int SMB2_SHAREFLAG_RESTRICT_EXCLUSIVE_OPENS = 0x100;
    /**
     * Share flag indicating that shared delete is forced for this share.
     */

                doClose();
                return null;
            }
            this.ridx = 0;
            return advance(true);
        }
        return null;
    }

    /**
     * Opens the enumeration and returns the first entry.
     *
     * @return the first file entry, or null if empty
     * @throws CIFSException if an error occurs during opening
     */

        final FileEntry[] results = this.response.getResults();
        if (results == null) {
            return new FileEntry[0];
        }
        return results;
    }

    /**
     * Opens a directory for enumeration
     *
     * @return the opened directory file entry
     * @throws CIFSException if an error occurs opening the directory
     */
    @SuppressWarnings("resource")
    @Override

        assertEquals(1, stats.totalSuccesses);
        assertEquals(0, stats.totalFailures);
        assertEquals(1.0, stats.successRate);
    }

    @Test
    @DisplayName("Test circuit opens after failure threshold")
    void testCircuitOpensAfterThreshold() {
        // Fail 3 times to open the circuit
        for (int i = 0; i < 3; i++) {
            try {
                circuitBreaker.call(() -> {

 *
 * <p>
 * There are three Win32 function calls provided by the Windows SDK
 * that are important in the context of using jCIFS. They are:
 *
 * <ul>
 * <li><code>CallNamedPipe</code> A message-type pipe call that opens,
 * writes to, reads from, and closes the pipe in a single operation.
 * <li><code>TransactNamedPipe</code> A message-type pipe call that
 * writes to and reads from an existing pipe descriptor in one operation.