Details
Improvement
Major
Description
The ResourceDispatcher is invoked outside of JSF lifecycle but we should avoid working with the FacesContext since this is not a JSF request. Instead, we should make the HttpServletRequest, HttpServletResponse, and ServletContext available to the application code.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
If they are unable to use push, an alternative approach may be to use a commandButton on the page to initiate the download, the action event for the commandButton would clear the messages and then set some JavaScript to be executed when the response is processed in the browser (JavaScriptContext.runScript()) that would synthetically press the outputResource link (which could be hidden on the page).
Show
Ken Fyten
added a comment - If they are unable to use push, an alternative approach may be to use a commandButton on the page to initiate the download, the action event for the commandButton would clear the messages and then set some JavaScript to be executed when the response is processed in the browser (JavaScriptContext.runScript()) that would synthetically press the outputResource link (which could be hidden on the page).
Adding these APIs will not provide the customer with what they require, after reviewing the SalesForce case. See suggested workarounds above.
I do not see how making HttpServletRequest and HttpServletResponse available to the ice:outputResource user solve the problem in this case.
The simplest solution would be to push an update, this way a new FacesContext will be created without the messages put in the previous one. The update will thus clear the messages rendered previously.