}
        }
    }

    @Test
    public void test_getSearchEngineHttpAddress_withSpecialCharacters() {
        String testAddress = "https://search-engine.example.com:9200/path?param=value&other=test";
        String originalValue = System.getProperty(Constants.FESS_SEARCH_ENGINE_HTTP_ADDRESS);

        try {

Поскольку мы используем относительный URL, если ваш API расположен по адресу `https://example.com/`, то он будет ссылаться на `https://example.com/token`. А если ваш API расположен по адресу `https://example.com/api/v1/`, то он будет ссылаться на `https://example.com/api/v1/token`.

    }
  }

  public static class ImmutableMapEntryListGenerator
      implements TestListGenerator<Entry<String, Integer>> {

    @Override
    public SampleElements<Entry<String, Integer>> samples() {
      return new SampleElements<>(
          mapEntry("foo", 5),
          mapEntry("bar", 3),
          mapEntry("baz", 17),
          mapEntry("quux", 1),
          mapEntry("toaster", -2));
    }

---

But for this example, we'll use a very simple HTML document with some JavaScript, all inside a long string.

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

But it's the simplest way to focus on the server-side of WebSockets and have a working example:

 * saml.sp.base.url=https://your-fess-server.example.com
 * </pre>
 *
 * <h3>Option 2: Set individual SP URLs</h3>
 * <pre>
 * # SP Entity ID (Audience URI in IdP)
 * saml.sp.entityid=https://your-fess-server.example.com/sso/metadata
 *
 * # Assertion Consumer Service URL
 * saml.sp.assertion_consumer_service.url=https://your-fess-server.example.com/sso/
 *
 * # Single Logout Service URL

        // Test adding GAV elements with version
        DomUtils.addGAVElements(dependency, "org.example", "test-artifact", "1.0.0");

        String xmlOutput = DomUtils.toXml(doc);
        assertTrue(xmlOutput.contains("<groupId>org.example</groupId>"), "Should contain groupId");
        assertTrue(xmlOutput.contains("<artifactId>test-artifact</artifactId>"), "Should contain artifactId");

You also define in some way at which **moments** your app will send those requests or events.

And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this dependency with classifier
    is not the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testvalidpom</artifactId>

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this
    dependency is the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testinvalidpom</artifactId>

 *
 * <p>
 * It includes constructors to initialize these details and getter and setter
 * methods to access and modify them.
 * </p>
 *
 * <p>
 * Example usage:
 * </p>
 * <pre>
 * {@code
 * AuthScope authScope = new AuthScope("example.com", 80);
 * Credentials credentials = new UsernamePasswordCredentials("user", "password");
 * Hc4Authentication auth = new Hc4Authentication(authScope, credentials);
 * }