*/
    public SearchForm() {
    }

    /**
     * The search term field for related content.
     */
    public String term;

    /**
     * The content field for searching related content.
     */
    public String content;

 * The search form for Crawling Info.
 */
public class SearchForm {

    /**
     * Default constructor for SearchForm.
     */
    public SearchForm() {
    }

    /**
     * The session ID field for searching crawling information.
     */
    public String sessionId;

/**
 * The search form for Access Token.
 */
public class SearchForm {

    /**
     * Default constructor for SearchForm.
     */
    public SearchForm() {
    }

    /**
     * The ID field for searching access tokens.
     */
    public String id;

     */
    public SearchForm() {
    }

    /**
     * The search term field for related queries.
     */
    public String term;

    /**
     * The queries field for searching related queries.
     */
    public String queries;

     */
    public SearchForm() {
    }

    /**
     * The regular name field for duplicate host configuration.
     */
    public String regularName;

    /**
     * The duplicate host name field for searching duplicate hosts.
     */
    public String duplicateHostName;

* Bridging this into an OSGi system: if this could be done then we can basically take over p2

TODO

- dealing with processing of input and adapting GAVs before searching i.e. plugin groups in Maven and default searching
- how to deal with resolution from different places like local/remote/workspace
- how to incorporate the metadata processor to start with
- create a hook to programmatically configure the test

                        writer.flush();
                    }
                });
            }
            final String name = id.substring(0, id.length() - NDJSON_EXTENTION.length());
            if ("search_log".equals(name)) {
                return writeNdjsonResponse(id, getSearchLogNdjsonWriteCall());
            }
            if ("user_info".equals(name)) {

		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.favorite_log/favorite_log"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.search_log/search_log"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.user_info/user_info"</arg>
		</postConstruct>
	</component>

/**
 * Service class for managing group operations in the Fess application.
 * Provides CRUD operations for groups, including integration with LDAP manager
 * and user-group relationships. Handles group pagination, searching, and
 * maintaining data consistency between groups and associated users.
 */
public class GroupService {

    /** Behavior class for group database operations */
    @Resource
    protected GroupBhv groupBhv;

		If you want to exclude the upper and lower bounds, use "{}".
	</dd>
	<dt>Boost</dt>
	<dd>
		To boost a term use the "^" symbol with a boost factor (a number) at
		the end of the term you are searching.
		<pre>Fess^100</pre>
	</dd>
	<dt>Fuzzy</dt>
	<dd>
		To do a fuzzy search use the "~" symbol at the end of a single word
		term. For example to search for a term similar in spelling to "Fess"
		use the fuzzy search: