[
https://issues.apache.org/jira/browse/TOBAGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-996.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0-alpha-3
1.0.37
> NonFacesRequestServlet doesn't work proper with JSF 1.2
> -------------------------------------------------------
>
> Key: TOBAGO-996
> URL: https://issues.apache.org/jira/browse/TOBAGO-996
> Project: MyFaces Tobago
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.35, 1.0.36
> Environment: Tomcat 6.0.28, MyFaces 1.2.10
> Reporter: Sven Bunge
> Assignee: Volker Weber
> Priority: Minor
> Fix For: 1.0.37, 1.5.0-alpha-3
>
>
> We developed a servlet extending the NonFacesRequestServlet to answer
> NonFacesRequests with NonFacesResponses - but we need a FacesContext to
> access JSF-manages beans in our logic. Now we switched to JSF 1.2 and the
> Servlet return HTTP status 404 everytime.
> After a short period of investigation I think it is a problem to create a
> UIViewRoot and don't answer with a FacesResponse. - I removed the two lines:
> UIViewRoot view = viewHandler.createView(facesContext, viewId);
> facesContext.setViewRoot(view);
> and it works like a charm.
> I think an UIViewRoot is only needed to match some navigation rules. Maybe
> the creation could be done in a protected method that could I override - or
> it is created later if the response is not completed in
> invokeApplication-method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
