Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 1.7
-
Fix Version/s: 2.0-Alpha3, 2.0.0
-
Component/s: Framework
-
Labels:None
-
Environment:server
Description
Revisit and possibly implement a better mechanism of how to map extensions for JSF viewIDs.
Right now there are restrictions on what extension can be used. Only *.iface, *.jspx, *.xhtml pages will be handled relatively well. Also there should be only one authoritative place were the mappings are defined, mappings that can potentially define what ViewHandler should be used.
Something like:
D2DViewHandler : *.iface pages -> *.jspx files
D2DFaceletViewHandler: *.xhtml pages -> *.xhtml files
ViewHandlerImpl: *.jsf pages -> *.jsp files
Right now there are restrictions on what extension can be used. Only *.iface, *.jspx, *.xhtml pages will be handled relatively well. Also there should be only one authoritative place were the mappings are defined, mappings that can potentially define what ViewHandler should be used.
Something like:
D2DViewHandler : *.iface pages -> *.jspx files
D2DFaceletViewHandler: *.xhtml pages -> *.xhtml files
ViewHandlerImpl: *.jsf pages -> *.jsp files
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion