You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Merge the Smithy server into org.restlet.ext.smithy, on par with its client #1673
The experimental Smithy server (#1638) is a separate artifact, org.restlet.ext.smithy.server, with no module descriptor. Other extensions, such as gRPC, ship their client and server in one artifact. The server also lags behind the Smithy client of org.restlet.ext.smithy:
Client
Server
Artifact
org.restlet.ext.smithy
org.restlet.ext.smithy.server
SDK discovery
ClientTransportFactory named restlet
none: Server.builder() only finds the SDK's Netty server
Protocols tested
restJson1, RPCv2 CBOR
restJson1
Named modules
tested from a named consumer
class path only
Proposal
Move SmithyServerAdapter and its host into org.restlet.ext.smithy, and drop the org.restlet.ext.smithy.server artifact. Neither has been released yet. smithy-java 1.8.0's server-api and server-core split a package (smithy-java#1437), so server-core becomes an optional dependency kept on the class path. The named module compiles against it with --add-reads org.restlet.ext.smithy=ALL-UNNAMED, and named consumers do the same.
Add a ServerProvider named restlet, which Server.builder() discovers ahead of the Netty server, and a public SmithyServerBuilder with the Restlet settings: connector context (HTTP/2, TLS) and the adapter's limits.
Test RPCv2 CBOR on the server over HTTP/1.1 and HTTP/2, a named consumer hosting a service, and discovery on the class path.
Activity
Merge the Smithy server into the Smithy extension, on par with its cl…