return facadeSelectList(createCB(cbLambda));
    }

    public PagingResultBean<ScheduledJob> selectPage(CBCall<ScheduledJobCB> cbLambda) {
        // #pending same?
        return (PagingResultBean<ScheduledJob>) facadeSelectList(createCB(cbLambda));
    }

    public void selectCursor(CBCall<ScheduledJobCB> cbLambda, EntityRowHandler<ScheduledJob> entityLambda) {

        OptionalThing<Locale> result2 = provider.findBusinessLocale(null, mockRequestManager);
        OptionalThing<Locale> result3 = provider.findBusinessLocale(null, mockRequestManager);

        // Verify all return same result
        assertTrue(result1.isPresent());
        assertTrue(result2.isPresent());
        assertTrue(result3.isPresent());
        assertEquals(Locale.GERMANY, result1.get());

                .forEach(s -> buf.append(s));
        log(buf);
    }

    /**
     * Increments the thread reference count for the specified crawler object.
     * Used when the same object is being processed on multiple threads.
     *
     * @param keyObj the crawler object running on an additional thread
     */
    public void runOnThread(final Object keyObj) {

            }
        }

        /**
         * Deletes old documents from the search index.
         * This method removes documents that were indexed in previous
         * crawling sessions for the same data configuration, keeping
         * only the documents from the current session.
         *
         * <p>The deletion process:</p>
         * <ul>
         *   <li>Checks if old document deletion is enabled</li>

plugins in gradle/gradle, it's easy for an object to be created without applying its associated plugin. For instance, Spring has a plugin that uses the Checkstyle task directly without applying the Checkstyle plugin.

Until we can provide the same guarantees for core plugins, we need to be more conservative for existing classes and not follow best practices. This means conventions need to be set in both a plugin and the constructor. This keeps existing builds working, but it may complicate the...

 * to ensure thread isolation of bindings.</p>
 *
 * <p>Note on class-level isolation: Compiled Script classes are cached and reused.
 * Class-level state (static fields, metaclass mutations) persists across evaluations
 * of the same script. In Fess, scripts are short expressions configured by
 * administrators (e.g., "data1 &gt; 10", "10 * boost1 + boost2") and do not use
 * static state, so this is acceptable.</p>
 *

    public ListResultBean<User> selectList(CBCall<UserCB> cbLambda) {
        return facadeSelectList(createCB(cbLambda));
    }

    public PagingResultBean<User> selectPage(CBCall<UserCB> cbLambda) {
        // #pending same?
        return (PagingResultBean<User>) facadeSelectList(createCB(cbLambda));
    }

    public void selectCursor(CBCall<UserCB> cbLambda, EntityRowHandler<User> entityLambda) {

        Set<ConstraintViolation<ExtendedTestBean>> violations = validator.validate(bean);
        assertEquals(2, violations.size());
    }

    // Test multiple annotations on same field
    @Test
    public void test_multipleValidations() {
        MultiValidationBean bean = new MultiValidationBean();
        bean.setRequiredCron(null); // Violates NotNull

                if (sides.size() > 1) { // explicit mapping
                    if (sides.size() != 2) {
                        throw new DictionaryException("more than one explicit mapping specified on the same line");
                    }
                    final List<String> inputStrings = split(sides.get(0), ",");
                    inputs = new String[inputStrings.size()];

        int firstQueriesCount = testFacetInfo.getAddedQueries().size();

        // Call init again
        facetQueryView.init();

        // Size should remain the same
        assertEquals(firstSize, facetQueryView.getQueryMap().size());
        // But queries would be added again to FacetInfo (distinct handles duplicates)