# Custom Request and APIRoute class { #custom-request-and-apiroute-class }

In some cases, you may want to override the logic used by the `Request` and `APIRoute` classes.

In particular, this may be a good alternative to logic in a middleware.

For example, if you want to read or manipulate the request body before it is processed by your application.

/// danger

This is an "advanced" feature.

 */
package org.codelibs.fess.app.logic;

import org.codelibs.fess.mylasta.action.FessUserBean;
import org.dbflute.hook.AccessContext;
import org.dbflute.optional.OptionalThing;
import org.lastaflute.core.time.TimeManager;
import org.lastaflute.db.dbflute.accesscontext.AccessContextResource;

import jakarta.annotation.Resource;

/**
 * The logic for access context.
 */
public class AccessContextLogic {

        }
    }

    /**
     * Functional interface for building XContent with custom logic.
     * Allows clients to provide custom content building implementations.
     */
    public interface XContentBuilderCallback {
        /**
         * Applies custom logic to build XContent using the provided builder and parameters.
         *

    }

    // Additional tests could be added here if MsrpcSamrOpenAlias had more methods or complex logic.
    // For this specific class, the constructor is the main point of logic.

        assertTrue("OnConnectListener list should be thread-safe",
                fesenClient.onConnectListenerList instanceof java.util.concurrent.CopyOnWriteArrayList);
    }

    /**
     * Test: Retry logic correctly enforces maxRetryCount
     * Verifies that with maxRetryCount=5, the operation is tried exactly 6 times (initial + 5 retries)
     */
    @Test
    public void testRetryLogicMaxRetryCount() throws Exception {

plugins {
    id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin")
}

dependencies {
    implementation(projects.integrationTesting)

     * This test is indirect as the constructor would throw an exception.
     * We can't instantiate the class with null, so we can't directly test this method's behavior with null.
     * However, the constructor logic `!isCredentialTypeCorrect()` covers this.
     * If `new PacCredentialType(null)` throws, it implies `isCredentialTypeCorrect()` returned false for null.
     */
    @Test
    void testIsCredentialTypeCorrectWithNullData() {

        String adjustment = "";

        if (parent != null) {
            String childName = child.getArtifactId();

            /*
             * This logic (using filesystem, against wanted independence from the user environment) exists only for the
             * sake of backward-compat with 2.x (MNG-5000). In general, it is wrong to

plugins {
    id("gradlebuild.kotlin-shared-runtime")
}

description = "Provides Kotlin DSL code that is shared between build-logic and runtime"

dependencies {
    compileOnly(platform("gradlebuild:build-platform"))
    compileOnly(kotlin("stdlib"))
    compileOnly("org.ow2.asm:asm-tree")
    compileOnly("com.google.code.findbugs:jsr305")
    compileOnly("org.jspecify:jspecify")

- [ ] Implement lease break notification handling
- [ ] Modify SmbFile to support lease-based caching
- [ ] Add lease upgrade/downgrade logic
- [ ] Implement lease epoch tracking for v2 leases

#### 1.3 Integration Points
- Modify `Smb2CreateRequest` to include lease contexts
- Update `SmbFile` caching logic to use leases
- Add lease break handling in `SmbTransport`

---

### Phase 2: Persistent Handles