Skip to content

Commit

Permalink
Minor tweak for Spring 3.2 compatibility
Browse files Browse the repository at this point in the history
Update NavigationMethodOutcomeResolver to use ServletWebRequest as
ServletInvocableHandlerMethod no longer accepts NativeWebRequest in
Spring 3.2
  • Loading branch information
philwebb committed Mar 10, 2013
1 parent 61e2cfe commit 6bdc7b2
Showing 1 changed file with 1 addition and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,6 @@
import org.springframework.web.bind.support.WebArgumentResolver;
import org.springframework.web.bind.support.WebBindingInitializer;
import org.springframework.web.bind.support.WebDataBinderFactory;
import org.springframework.web.context.request.NativeWebRequest;
import org.springframework.web.context.request.ServletWebRequest;
import org.springframework.web.method.HandlerMethodSelector;
import org.springframework.web.method.annotation.ExpressionValueMethodArgumentResolver;
Expand Down Expand Up @@ -409,7 +408,7 @@ private NavigationOutcome resolve(FacesContext facesContext, NavigationMappingMe
invocable.setHandlerMethodReturnValueHandlers(this.returnValueHandlers);

ExternalContext externalContext = facesContext.getExternalContext();
NativeWebRequest request = new ServletWebRequest((HttpServletRequest) externalContext.getRequest(),
ServletWebRequest request = new ServletWebRequest((HttpServletRequest) externalContext.getRequest(),
(HttpServletResponse) externalContext.getResponse());
ModelAndViewContainer modelAndViewContainer = new ModelAndViewContainer();
invocable.invokeAndHandle(request, modelAndViewContainer);
Expand Down

0 comments on commit 6bdc7b2

Please sign in to comment.