Class ResourceReader
java.lang.Object
org.jboss.resteasy.reactive.common.model.ResourceReader
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic classThe comparison for now is simple: 1) Application provided writers come first 2) Readers with lower priority come first (same as reader interceptors) 3) Then the more specific the media type, the higher the priority 4) Finally we compare the number of media types The spec doesn't seem to mention this sorting being explicitly needed, but there are tests in the TCK that only pass reliably if the Readers are sorted like this -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionjakarta.ws.rs.RuntimeTypeBeanFactory<jakarta.ws.rs.ext.MessageBodyReader<?>>jakarta.ws.rs.ext.MessageBodyReader<?>instance()booleanbooleanmatchesRuntimeType(jakarta.ws.rs.RuntimeType runtimeType) List<jakarta.ws.rs.core.MediaType>setBuiltin(boolean builtin) setConstraint(jakarta.ws.rs.RuntimeType constraint) setFactory(BeanFactory<jakarta.ws.rs.ext.MessageBodyReader<?>> factory) setMediaTypeStrings(List<String> mediaTypeStrings) setPriority(Integer priority)
-
Constructor Details
-
ResourceReader
public ResourceReader()
-
-
Method Details
-
setFactory
-
getFactory
-
getMediaTypeStrings
-
setMediaTypeStrings
-
getConstraint
public jakarta.ws.rs.RuntimeType getConstraint() -
setConstraint
-
isBuiltin
public boolean isBuiltin() -
setBuiltin
-
getPriority
-
setPriority
-
instance
public jakarta.ws.rs.ext.MessageBodyReader<?> instance() -
mediaTypes
-
matchesRuntimeType
public boolean matchesRuntimeType(jakarta.ws.rs.RuntimeType runtimeType)
-