
eap7.eap6.resteasy.windup.xml Maven / Gradle / Ivy
The newest version!
This ruleset provides analysis of JBoss EAP 6 and RESTEasy 2 which needs to be replaced when migrating to JBoss EAP 7+ and RESTEasy 3+.
resteasy
Caching in the RESTEasy client framework in resteasy-jaxrs is replaced by caching in the JAX-RS 2.0 compliant resteasy-client module.
Use `org.jboss.resteasy.client.jaxrs.cache` package instead of `org.jboss.resteasy.client.cache`.
resteasy
; rel="previous";
title="previous chapter">").post(Entity.text(new String()));
javax.ws.rs.core.Link link = response.getLink("previous");
```
]]>
resteasy
Replace `org.jboss.resteasy.client.ClientResponse` class with `javax.ws.rs.core.Response`.
resteasy
Replace this class with `org.jboss.resteasy.client.jaxrs.{type}`.
resteasy
` is a generic type in the RESTEasy client framework,
but `org.jboss.resteasy.client.jaxrs.internal.ClientResponse` in the resteasy-client module is not, so
`EntityTypeFactory` is no longer useful.
]]>
resteasy
Replace the `org.jboss.resteasy.client.ClientExecutor` usage with `org.jboss.resteasy.client.jaxrs.ClientHttpEngine` class.
resteasy
Replace the `org.jboss.resteasy.client.ClientRequestFactory` usage with `org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder` class.
resteasy
Replace the `org.jboss.resteasy.client.ClientResponseFailure` with `javax.ws.rs.client.ResponseProcessingException`
or with `javax.ws.rs.client.ProcessingException` or with `javax.ws.rs.client.WebApplicationException` class.
resteasy
Replace `org.jboss.resteasy.spi.StringConverter` by `javax.ws.rs.ext.ParamConverterProvider`.
resteasy
There were multiple changes on adding/removing methods on `org.jboss.resteasy.spi.InjectorFactory`.
resteasy
The interface `org.jboss.resteasy.spi.interception.MessageBodyWriterInterceptor` is deprecated and you should use `javax.ws.rs.ext.WriterInterceptor` from JAX-RS API.
resteasy
The interface `org.jboss.resteasy.spi.interception.MessageBodyReaderInterceptor` is deprecated and you should use `javax.ws.rs.ext.ReaderInterceptor` from JAX-RS API.
resteasy
The interface `org.jboss.resteasy.spi.interception.MessageBodyWriterContext` is replaced by the `javax.ws.rs.ext.WriterInterceptorContext` interface by JAX-RS 2.0 compliant interceptor facility.
resteasy
`org.jboss.resteasy.core.interception.InterceptorRegistry` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.
resteasy
`org.jboss.resteasy.core.interception.InterceptorRegistryListener` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.
resteasy
No direct replacement.
resteasy
Use `javax.ws.rs.container.DynamicFeature` for Dynamic binding instead of implementing `org.jboss.resteasy.spi.interception.AcceptedByMethod` interface.
resteasy
Remove annotation `@org.jboss.resteasy.annotations.cache.ServerCached' as it was removed in RESTEasy 3.x.
resteasy
Replaced by `javax.ws.rs.core.Link` in JAX-RS API.
resteasy
jax-rs
`org.jboss.resteasy.spi.interception.ClientExecutionContext` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.
resteasy
Use `javax.ws.rs.client.Invocation` instead of `org.jboss.resteasy.spi.interception.ClientExecutionInterceptor`.
The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
resteasy
METHOD_CALL
Most of the `org.jboss.resteasy.spi.ResteasyProviderFactory#add*` methods have been removed or made protected in RESTEasy 3.0.
For example, the `addBuiltInMessageBodyReader()` and `addBuiltInMessageBodyWriter()` methods have been removed and the `addMessageBodyReader()` and `addMessageBodyWriter()` methods have been made protected.
You should now use the `registerProvider()` and `registerProviderInstance()` methods.
resteasy
Use `javax.ws.rs.ext.ReaderInterceptorContext` instead of `org.jboss.resteasy.spi.interception.MessageBodyReaderContext`.
The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
resteasy
Use `javax.ws.rs.container.ContainerResponseFilter` instead of `org.jboss.resteasy.spi.interception.PostProcessInterceptor`.
The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant filters and interceptor facility in release 3.0.x.
resteasy
Use `javax.ws.rs.container.ContainerRequestFilter` instead of `org.jboss.resteasy.spi.interception.PreProcessInterceptor`.
The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant filters and interceptor facility in release 3.0.x.
resteasy
There were multiple changes on adding/removing methods on `org.jboss.resteasy.spi.Registry`.
resteasy
Replaced by `javax.ws.rs.ForbiddenException` in jaxrs-api module.
resteasy
jax-rs
Replaced by `javax.ws.rs.NotAllowedException` in jaxrs-api module.
resteasy
jax-rs
Replaced by `javax.ws.rs.NotAcceptableException` in jaxrs-api module.
resteasy
jax-rs
Replaced by `javax.ws.rs.NotFoundException` in jaxrs-api module.
resteasy
jax-rs
Replaced by `javax.ws.rs.NotAuthorizedException` in jaxrs-api module.
resteasy
jax-rs
Replaced by `javax.ws.rs.NotSupportedException` in jaxrs-api module.
resteasy
jax-rs
METHOD_CALL
RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.delegates.ServerCookie#checkName` without a replacement.
It was deprecated in the original `org.apache.tomcat.util.http.ServerCookie` class which was a template for this method.
resteasy
METHOD_CALL
Empty
resteasy
METHOD_CALL
Replace method calls of `encodeRedirectUrl` with `encodeRedirectURL(String url)`.
resteasy
METHOD_CALL
Replace `ResteasyHttpServletResponseWrapper#encodeUrl` with `ResteasyHttpServletResponseWrapper#encodeURL(String url)`.
resteasy
METHOD_CALL
`MultipartFormDataInputImpl#getFormData` method will be removed in the future. Use `MultipartFormDataInput#getFormDataMap()` instead.
resteasy
METHOD_CALL
`MultipartFormDataInput#getFormData` method will be removed in the future. Use `MultipartFormDataInput#getFormDataMap()` instead.
resteasy
METHOD_CALL
As of Version 2.1 of the Java Servlet API, use `ResteasyHttpServletRequestWrapper.isRequestedSessionIdFromURL()` instead.
resteasy
METHOD_CALL
Method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#isValidating` is deprecated without a replacement.
resteasy
METHOD_CALL
RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.delegates.ServerCookie#maybeQuote` without a replacement.
It was deprecated in the original `org.apache.tomcat.util.http.ServerCookie` class which was a template for this method.
resteasy
METHOD_CALL
Method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#setAdapter` is deprecated in RESTEasy 3.
resteasy
METHOD_CALL
As of version 2.1, due to ambiguous meaning of the message parameter. To set a status code use `setStatus(int)` instead,
to send an error with a description use `sendError(int, String)`. Sets the status code and message for this response.
resteasy
METHOD_CALL
RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#setValidating` without a replacement.
resteasy
METHOD_CALL
RESTEasy 3 deprecates `org.jboss.resteasy.auth.oauth.OAuthValidator#validateMessage` method without a replacement.
resteasy
ANNOTATION
The resteasy-yaml-provider module is not recommended to use due security issue in SnakeYAML library used by RESTEasy for unmarshaling.
If you would like to use YAML Resteasy Provider even it is not recommended,
you need to add the SnakeYAML library (Maven dependency) into your application and enable it by creating file `META-INF/services/javax.ws.rs.ext.Providers` with line `org.jboss.resteasy.plugins.providers.YamlProvider` in that file and your application.
resteasy
yaml
ANNOTATION
ANNOTATION
Deserializing Java objects from untrusted sources is not safe. For this reason,
the `org.jboss.resteasy.plugins.providers.SerializableProvider` class is disabled by default, and it is not recommended to use this provider.
If you need to enable it even against the recommendation, create or update file `META-INF/services/javax.ws.rs.ext.Providers` with adding line with `org.jboss.resteasy.plugins.providers.SerializableProvider` string.
resteasy
ANNOTATION
ANNOTATION
RESTEasy fixes the issue when it doesn't set/add correctly character set meta data specified in JAX-RS specification. Therefore UTF-8 as the character set for text media types is set by default.
This behavior results in adding `charset=UTF-8` string to the returned content-type header when the resource method returns a `text/*` or `application/xml*` media type without an explicit charset.
The behavior is controlled by `resteasy.add.charset` parameter which is set to `true` by default and you can customize the `resteasy.add.charset` parameter to `false` in _web.xml_'s `context-param` element
in case of wanting to keep previous behavior.
resteasy
charset
© 2015 - 2025 Weber Informatics LLC | Privacy Policy