Soklet Servlet Integration (jakarta) 2.0.0 API

Soklet

Soklet is not a Servlet Container - it has its own in-process HTTP server, its own approach to request and response constructs, and so forth. Soklet applications are intended to be "vanilla" Java applications, as opposed to a WAR file deployed onto a Java EE App Server.

However, there is a large body of existing code that relies on the Servlet API. To support it, Soklet provides its own implementations of the following Servlet interfaces, which enable interoperability for many common use cases: This library is for the jakarta.servlet API. If you need to integrate with the legacy javax.servlet API, use soklet-servlet-javax.

Version 2.0.0 requires Soklet 4.0.0 or later and is incompatible with Soklet 3.x. Query parameters use UTF-8 independently of body encoding; unspecified body encodings retain the Servlet ISO-8859-1 fallback. Sessions copy the context timeout when created, but applications remain responsible for persistence and expiration.

Response adapters capture their entire body in memory and copy it into a finite Soklet response. Flush and commitment affect only local adapter state, not network delivery. The configured buffer size is a commit threshold, not a body or memory limit. There is no native streaming response-adapter mode; bound generated output in the application and use native file responses, HTTP streaming, or Server-Sent Events for large files or live feeds. See response buffering guidance.

Please refer to the official documentation at https://www.soklet.com/docs/servlet-integration.

Packages
Package
Description
Contains Soklet-aware implementations of Servlet interfaces.