Issue Details (XML | Word | Printable)

Key: SHALE-178
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Craig McClanahan
Reporter: Ed Burns
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Shale

Shale Remoting doesn't support multiple instances of the FacesServlet, for example in the case of AJAX

Created: 16/May/06 04:25 AM   Updated: 21/Aug/06 11:28 PM
Component/s: Remoting
Affects Version/s: 1.0.3-SNAPSHOT
Fix Version/s: 1.0.3

File Attachments:
  Size
Text File Licensed for inclusion in ASF works diffs.txt 2006-05-16 04:27 AM Ed Burns 4 kB

Flags: Patch


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Ed Burns added a comment - 16/May/06 04:27 AM
Fix for this bug, first iteration.

Craig McClanahan added a comment - 18/May/06 12:35 AM
Ed's approach looks reasonable on the surface ... will evaluate in detail and commit after JavaOne.

Craig McClanahan added a comment - 23/May/06 12:28 PM
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.

Craig McClanahan added a comment - 23/May/06 12:32 PM
Resolved in nightly build 20060523 via minor docco tweaks to the supplied patch. Thanks!