"groovy",
            "groovyjarjarantlr",
            "net/rubygrapefruit",
            "org/codehaus/groovy",
            "org/apache/groovy",
            "org/apache/tools/ant",
            "org/apache/commons/logging",
            "org/jetbrains/annotations",
            "org/jspecify/annotations",
            "org/slf4j",
            "org/apache/log4j",
            "org/apache/xerces",
            "org/w3c/dom",

{* ../../docs_src/server_sent_events/tutorial001_py310.py ln[34:37] hl[35] *}

## `ServerSentEvent` { #serversentevent }

Wenn Sie SSE-Felder wie `event`, `id`, `retry` oder `comment` setzen müssen, können Sie statt reiner Daten `ServerSentEvent`-Objekte yielden.

Importieren Sie `ServerSentEvent` aus `fastapi.sse`:

{* ../../docs_src/server_sent_events/tutorial002_py310.py hl[4,26] *}

# Utiliser des dataclasses { #using-dataclasses }

FastAPI est construit au‑dessus de **Pydantic**, et je vous ai montré comment utiliser des modèles Pydantic pour déclarer les requêtes et les réponses.

Mais FastAPI prend aussi en charge l'utilisation de [`dataclasses`](https://docs.python.org/3/library/dataclasses.html) de la même manière :

{* ../../docs_src/dataclasses_/tutorial001_py310.py hl[1,6:11,18:19] *}

{* ../../docs_src/server_sent_events/tutorial001_py310.py ln[34:37] hl[35] *}

## `ServerSentEvent` { #serversentevent }

Se você precisar definir campos de SSE como `event`, `id`, `retry` ou `comment`, você pode produzir objetos `ServerSentEvent` em vez de dados simples.

Importe `ServerSentEvent` de `fastapi.sse`:

{* ../../docs_src/server_sent_events/tutorial002_py310.py hl[4,26] *}

import static java.util.concurrent.TimeUnit.SECONDS;

import com.google.common.annotations.GwtIncompatible;
import com.google.common.annotations.J2ktIncompatible;
import com.google.common.base.Preconditions;
import com.google.common.base.Stopwatch;
import com.google.common.testing.NullPointerTester;
import com.google.common.testing.TearDownStack;
import com.google.errorprone.annotations.CanIgnoreReturnValue;

			Description: `use StartTLS connection to AD/LDAP server` + defaultHelpPostfix(ServerStartTLS),
			Optional:    true,
			Type:        "on|off",
		},
		config.HelpKV{
			Key:         config.Comment,
			Description: config.DefaultComment,
			Optional:    true,
			Type:        "sentence",
		},
	}

    $ mvn rpm:rpm   # pacote .rpm
    $ mvn jdeb:jdeb # pacote .deb

### Gerar Código Fonte

    $ mvn dbflute:download # (comando executado uma vez)
    $ mvn dbflute:freegen
    $ mvn license:format

### Testes de Integração

Inicie o servidor Fess e execute o seguinte comando:

    $ mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201"

        assertEquals("\\Qfile://test\\E.*", parser.parseFilterPaths("file://test", true, false));
        assertEquals("\\Qtest\\E", parser.parseFilterPaths("test", true, false));
        assertEquals("", parser.parseFilterPaths("# comment\n\n  ", true, false));
    }

    @Test
    public void test_parseFilterPaths_file() {
        GsaConfigParser parser = new GsaConfigParser();

- **EncodingHelper**: Charset detection with BOM
- **UrlConvertHelper**: URL normalization
- **ContentLengthHelper**: Content length limits per MIME type

---

## Development Workflow

### Build Commands

```bash
mvn clean install              # Build all
mvn clean install -DskipTests  # Skip tests
mvn test                       # Run tests
mvn formatter:format           # Format code

Core attributes: `text`, `timestamp`, `queryFreq`, `docFreq`, `userBoost`, `readings`, `tags`, `roles`, `languages`, `kinds`

Kind types: `DOCUMENT`, `QUERY`, `USER`

---

## Development Workflow

### Build Commands

```bash
mvn compile                              # Compile
mvn test                                 # Run all tests
mvn test -Dtest=SuggesterTest           # Run specific test