But this example is still valid and it shows how to interact with the internal components.

///

We can also use this same approach to access the request body in an exception handler.

All we need to do is handle the request inside a `try`/`except` block:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

     * when effectiveModel is null, addressing issue #11292.
     */
    @Test
    void testExtractProjectIdFallback() throws Exception {
        // Use reflection to access the private extractProjectId method
        Method extractProjectIdMethod =
                DefaultProjectBuilder.class.getDeclaredMethod("extractProjectId", ModelBuilderResult.class);

## Submitting PRs

1. **Title and Summary**:
   - Use a scannable title: `[Subsystem] Action Description #Issue` (e.g., `[IAM] Add role-based access control #567`).
   - Include context in the summary: what changed, why, and any issue references.
   - Use `[WIP]` for in-progress PRs to avoid premature merging or choose GitHub draft PRs.

2. **Commits**:

     *         {@code null}.
     * @throws ProjectBuildingException If an error was encountered during building of any project.
     *             {@link ProjectBuildingException#getResults()} provides access to the details of the problems.
     */
    List<ProjectBuildingResult> build(List<File> pomFiles, boolean recursive, ProjectBuildingRequest request)
            throws ProjectBuildingException;

		return nil, errors.New("both the token file and the role ARN are required")
	case conf.AccessKey == "" && conf.SecretKey != "" || conf.AccessKey != "" && conf.SecretKey == "":
		return nil, errors.New("both the access and secret keys are required")
	case conf.AWSRole && (conf.AWSRoleWebIdentityTokenFile != "" || conf.AWSRoleARN != "" || conf.AccessKey != "" || conf.SecretKey != ""):

   * within VarHandleAtomicHelper and AtomicReferenceFieldUpdaterAtomicHelper.
   *
   * Package-private "shouldn't" be necessary: The *AtomicHelper classes and AbstractFutureState
   * "should" be nestmates, so a call to MethodHandles.lookup or
   * AtomicReferenceFieldUpdater.newUpdater inside *AtomicHelper "should" have access to

     * This provides database operations for RelatedQuery entities.
     */
    @Resource
    protected RelatedQueryBhv relatedQueryBhv;

    /**
     * Configuration properties for Fess application.
     * Used to access various configuration settings like paging parameters.
     */
    @Resource
    protected FessConfig fessConfig;

    /**
     * Retrieves a paginated list of related queries based on the provided pager parameters.

        Assertions.assertEquals(1_700_000_000_000L, info.getLastWriteTime(), "last write should match");
        Assertions.assertEquals(1_650_000_000_000L, info.getLastAccessTime(), "last access should match");
        Assertions.assertEquals(42L, info.getSize(), "size should match");
    }

    // --- Parameterized: edge and boundary values across getters ---

           * well be a JDK bug.
           */
          || info.getName().contains("TypeTokenTest")
          /*
           * "IllegalAccess tried to access class
           * com.google.common.collect.testing.AbstractIteratorTester from class
           * com.google.common.collect.MultimapsTest"
           *
           * ...when we build with JDK 22 and run under JDK 8.

 * quickly, since the row key is provided. However, {@code column(columnKey).size()} takes longer,
 * since an iteration across all row keys occurs.
 *
 * <p>Note that this implementation is not synchronized. If multiple threads access this table
 * concurrently and one of the threads modifies the table, it must be synchronized externally.
 *
 * <p>See the Guava User Guide article on <a href=