* #stopAsync()} lifecycle methods to transition between states. Example services include
 * webservers, RPC servers and timers.
 *
 * <p>The normal lifecycle of a service is:
 *
 * <ul>
 *   <li>{@linkplain State#NEW NEW} -&gt;
 *   <li>{@linkplain State#STARTING STARTING} -&gt;
 *   <li>{@linkplain State#RUNNING RUNNING} -&gt;

        TestTransformer transformer = new TestTransformer();
        assertNotNull(transformer);
        assertNull(transformer.getName());
    }

    /**
     * Test getName and setName with normal values
     */
    public void test_name_getterSetter() {
        // Initial state
        assertNull(testTransformer.getName());

        // Set name
        testTransformer.setName("testTransformer");

dation~="recaptcha"]',b).each(function(){var d=a(this),e=document.createElement("DIV"),f=c.reCaptchaSiteKey||d.valAttr("recaptcha-sitekey"),g=c.reCaptchaTheme||d.valAttr("recaptcha-theme")||"light",h=c.reCaptchaSize||d.valAttr("recaptcha-size")||"normal",i=c.reCaptchaType||d.valAttr("recaptcha-type")||"image";if(!f)throw new Error("Google reCaptcha site key is required.");var j=grecaptcha.render(e,{sitekey:f,theme:g,size:h,type:i,callback:function(a){b.find('[data-validation~="recaptcha"]').trig...

* `HEAD`
* `PATCH`
* `TRACE`

In the HTTP protocol, you can communicate to each path using one (or more) of these "methods".

---

When building APIs, you normally use these specific HTTP methods to perform a specific action.

Normally you use:

* `POST`: to create data.
* `GET`: to read data.
* `PUT`: to update data.
* `DELETE`: to delete data.

          "synonyms_path": "${fess.dictionary.path}synonym.txt"
        }
      },
      "tokenizer": {
        "japanese_tokenizer": {
          "type": "fess_japanese_tokenizer",
          "mode": "normal",
          "user_dictionary": "${fess.dictionary.path}ja/kuromoji.txt",
          "discard_punctuation": false
        },
        "korean_tokenizer": {
            "type": "fess_korean_tokenizer",

        }
    }

    @Test
    @DisplayName("Zero-length message is handled correctly")
    void zeroLengthMessageHandled() throws IOException {
        // Create a zero-length message followed by a normal message
        byte[] data = new byte[] { 10, 20 };
        byte[] fullData = concat(messageHeader(0), // Zero-length message
                messageHeader(2), data);

        assertEquals("MatchAllDocsQuery", className);
        assertEquals(MatchAllDocsQuery.class.getSimpleName(), className);
    }

    public void test_execute() {
        // Test execute method with normal parameters
        QueryContext context = new QueryContext("*:*", false);
        MatchAllDocsQuery query = new MatchAllDocsQuery();
        float boost = 1.0f;

     * registers popular words if enabled.
     *
     * @param runtime the action runtime context
     * @return the action response, or null to continue with normal processing
     */
    @Override
    public ActionResponse hookBefore(final ActionRuntime runtime) { // application may override
        searchLogSupport = fessConfig.isSearchLog();

     * This method will attempt
     * to resolve SIDs using a cache and cache the results of any SIDs that
     * required resolving with the authority. SID cache entries are currently not
     * expired because under normal circumstances SID information never changes.
     *
     * @param authorityServerName
     *            The hostname of the server that should be queried. For maximum efficiency this should be the hostname

### Import `HTTPException` { #import-httpexception }

{* ../../docs_src/handling_errors/tutorial001.py hl[1] *}

### Raise an `HTTPException` in your code { #raise-an-httpexception-in-your-code }

`HTTPException` is a normal Python exception with additional data relevant for APIs.

Because it's a Python exception, you don't `return` it, you `raise` it.