// the operation would be a no-op, so exceptions are allowed but not required
    }
    expectUnchanged();
  }

  @MapFeature.Require(absent = SUPPORTS_PUT)
  public void testReplaceEntry_unsupportedAbsentKey() {
    try {
      getMap().replace(k3(), v3(), v4());
    } catch (UnsupportedOperationException tolerated) {

But you can also declare the `Response` that you want to be used (e.g. any `Response` subclass), in the *path operation decorator* using the `response_class` parameter.

The contents that you return from your *path operation function* will be put inside of that `Response`.

 */
package org.codelibs.fess.exception;

/**
 * An exception thrown when an LDAP operation fails.
 */
public class LdapOperationException extends FessSystemException {

    private static final long serialVersionUID = 1L;

    /**
     * Constructs a new LDAP operation exception with the specified detail message and cause.
     *
     * @param message The detail message.

      int iterations = 100000;
      int nKeys = keys.size();
      int[] deltas = new int[nKeys];
      Operation[] operations = Operation.values();
      for (int i = 0; i < iterations; i++) {
        int keyIndex = random.nextInt(nKeys);
        String key = keys.get(keyIndex);
        Operation op = operations[random.nextInt(operations.length)];
        switch (op) {
          case ADD:
            {

 * It keeps track of any failures that occur during the operation.
 */
public class SuggestWriterResult {
    /**
     * Constructs a new {@link SuggestWriterResult}.
     */
    public SuggestWriterResult() {
        // nothing
    }

    /**
     * A list of Throwables representing failures that occurred during the operation.
     */

    }

    /**
     * Returns a {@link CopyOptions} with the specified property names to include in the operation.
     *
     * @param propertyNames
     *            An array of property names. Must not be {@literal null} or an empty array.
     * @return A {@link CopyOptions} with the specified property names to include in the operation.
     * @see CopyOptions#include(CharSequence...)
     */

Swagger UI lo manejará detrás de escena para ti, pero necesita este auxiliar de "redirección".

///

### Crea una *path operation* para probarlo { #create-a-path-operation-to-test-it }

Ahora, para poder probar que todo funciona, crea una *path operation*:

{* ../../docs_src/custom_docs_ui/tutorial001_py39.py hl[36:38] *}

### Pruébalo { #test-it }

        smbRandomAccessFile.seek(-1);
        assertEquals(-1, smbRandomAccessFile.getFilePointer());
    }

    @Test
    void testReadByte() throws SmbException {
        // Mock the read operation to return a specific byte
        doAnswer(new Answer<Void>() {
            @Override
            public Void answer(InvocationOnMock invocation) throws Throwable {

* It takes each **request** that comes to your application.
* It can then do something to that **request** or run any needed code.
* Then it passes the **request** to be processed by the rest of the application (by some *path operation*).

{* ../../docs_src/security/tutorial002_an_py310.py hl[30:32] *}

## Recap { #recap }

You can now get the current user directly in your *path operation function*.

We are already halfway there.

We just need to add a *path operation* for the user/client to actually send the `username` and `password`.