Container implementations use the {@code ApplicationHandler} API to process requestsby invoking the {@link #handle(ContainerRequest) handle(request)}method on a configured application handler instance.
{@code ApplicationHandler} provides two implementations of {@link javax.ws.rs.core.Configuration config} that can be injectedinto the application classes. The first is {@link ResourceConfig resource config} which implements {@code Configuration}itself and is configured by the user. The resource config is not modified by this application handler so the future reloads of the application is not disrupted by providers found on a classpath. This config can be injected only as {@code ResourceConfig} or {@code Application}. The second one can be injected into the {@code Configuration} parameters / fields and contains info about all the properties / provider classes / provider instancesfrom the resource config and also about all the providers found during processing classes registered under {@link ServerProperties server properties}. After the application handler is initialized both configurations are marked as read-only.
@author Pavel Bucek (pavel.bucek at oracle.com) @author Jakub Podlesak (jakub.podlesak at oracle.com) @author Marek Potociar (marek.potociar at oracle.com) @author Libor Kramolis (libor.kramolis at oracle.com) @see ResourceConfig @see javax.ws.rs.core.Configuration @see org.glassfish.jersey.server.spi.ContainerProvider
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|