-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
7.0.0.ER6
-
None
Some modules of providers are public in EAP. Is this visibility correct? Modules should be private, if user don't directly interact with any of classes from module.
- resteasy-json-p-provider
- Users could create new provider, that extends AbstractJsonpProvider
- com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider
- jackson-jaxrs-base-2.5.4.redhat-1.jar
- jackson-jaxrs-json-provider-2.5.4.redhat-1.jar
- Users could create new provider, that extends JacksonJaxbJsonProvider or JacksonJsonProvider
- jackson-module-jaxb-annotations-2.5.4.redhat-1.jar
- com.fasterxml.jackson.core.jackson-databind
- com.fasterxml.jackson.core.jackson-core
Anyway, com.fasterxml.jackson.* modules could be used also without RESTEasy.
Other public providers should stay public:
- resteasy-validator-provider-11
- EAP application can use RE client to send request to some rest service. If validation error occurs, RE client in EAP application can use ResteasyViolationException class to get information about error
- resteasy-atom-provider
- object model from these provider could be used directly by user, like Feed or Entry class
- resteasy-jettison-provider, resteasy-jackson-provider, resteasy-jackson2-provider, resteasy-jaxb-provider, resteasy-multipart-provider
- some annotations from these modules could be used directly by user
- com.fasterxml.jackson.core.jackson-annotations
- JsonProperty, JsonSubTypes and JsonTypeInfo annotation could be used in deployment
- relates to
-
JBEAP-65 Jackson libs are Private, should be Public
- Closed
-
RESTEASY-1533 Public / private module separation
- Resolved