[ http://issues.apache.org/struts/browse/SHALE-178?page=all ]
Craig McClanahan updated SHALE-178:
-----------------------------------
type: Improvement (was: Bug)
Reclassifying as an "improvement" because multiple FacesServlet instances
actually were supported ... but the selection of the servlet definition to use
was positional (the last one was selected). The improvement will allow you to
declare the servlet name of the servlet definition to be used, independent of
ordering in the deployment descriptor.
> Shale Remoting doesn't support multiple instances of the FacesServlet, for
> example in the case of AJAX
> ------------------------------------------------------------------------------------------------------
>
> Key: SHALE-178
> URL: http://issues.apache.org/struts/browse/SHALE-178
> Project: Shale
> Type: Improvement
> Components: Remoting
> Versions: 1.0.3
> Reporter: Ed Burns
> Assignee: Craig McClanahan
> Attachments: diffs.txt
>
> JSF 1.2 allows mapping the FacesServlet more than once in one webapp, with
> each one having a different lifecycle ID. This enables JSF to have an AJAX
> JSF servlet, and a "regular" JSF servlet. However, shale remoting assumes
> that there is only one faces Servlet mapped.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
