DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38190>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38190 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-09 05:13 ------- (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > Actually you can override it, with a context init parameter whose name is > ViewHandler.DEFAULT_SUFFIX_PARAM_NAME (javax.faces.DEFAULT_SUFFIX). If you do > not override, the default value is ".jsp". I guess my point is, why couldn't you choose to use jsp, clay full XML and HTML views in a single application. Three types of entry points all responsible for creating a JSF view. The single parameter implies that only one type is possible. Clay handles this by rewriting the view id which seems to work most of the time. The faces servlet is mapped to "*.faces", "*.xml" and "*.html". It seems like the view id should be controlled by the instance of the view handler verses it's caller. I'd also like to see a more standardized approach for how the JSP Tag's track the component's as they get built. It would be nice if you could use a RequestDispatcher to include a faces jsp view from another type of JSF view technology (like from a clay full html or xml view). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
