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=38970>. 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=38970 ------- Additional Comments From [EMAIL PROTECTED] 2006-03-14 23:39 ------- (In reply to comment #0) > When testing the following Clay examples from the shale-usecases example > application: > Symbols - pages 1, 2, and 3 > Full HTML View > Extreme HTML View > Full XML View > I see, at the end of the page, 'com.sun.faces.saveState.FieldMarker'. > I don't see this when running the Clay JSP view. > To reproduce: Deploy the shale-usecases application to a nightly build of > GlassFish and run one of the examples mentioned above. Clay has not been refactored to support JSF 1.2. In JSF 1.1, the JSP "ViewTag" tag handles searching through the rendered response stream replacing the "com.sun.faces.saveStateFieldMarker" marker within the HTML form tag with the serialized client state as a hidden input field. The marker is not standardized under 1.1 and is called "<!-- @@JSF_FORM_STATE_MARKER@@-->" in myfaces. When using Clay full HTML or XML views, the Clay View handler has this responsibility since the page doesn't have a JSP "ViewTag" tag. >From what I understand, JSF 1.2 moves this responsibility to the ViewHandler and the marker name is standardized. JSF 1.2 also handles the interweaving of non-JSF jsp with JSF component rendered output differently too. We will have to address this issue when committing to support JSF 1.2. Thanks for the feedback. -- 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]
