-
Bug
-
Resolution: Done
-
Major
-
3.1.0.Final
The code in ResteasyBootstrap used to register (among other things) the dispatcher and the registry:
servletContext.setAttribute(ResteasyProviderFactory.class.getName(), deployment.getProviderFactory()); servletContext.setAttribute(Dispatcher.class.getName(), deployment.getDispatcher()); servletContext.setAttribute(Registry.class.getName(), deployment.getRegistry());
these instances are then expected to be found and then re-used by the servlet dispatcher:
ResteasyProviderFactory globalFactory = (ResteasyProviderFactory) servletContext.getAttribute(ResteasyProviderFactory.class.getName()); Dispatcher globalDispatcher = (Dispatcher) servletContext.getAttribute(Dispatcher.class.getName());
This used to be the case in versions before 3.1.0.Final - as of then, the ResteasyBootstrap only registers the deployment, but the code in the ServletContainerDispatcher has not changed. This means, that now instead of using the same registry where all the Spring beans are registered, a new (and empty) registry is used, thus making the Spring beans inaccessible
- is caused by
-
RESTEASY-1287 RESTEasy-Spring is unable to set mediaTypeMappings in ResteasyDeployment by bean settings
- Resolved
- relates to
-
RESTEASY-1592 ResteasyServletContainerInitializer and ConfigurationBootstrap do not access the same initialization parameters
- Closed