[ http://issues.apache.org/struts/browse/SHALE-67?page=comments#action_38433 ] Gary VanMatre commented on SHALE-67: ------------------------------------
I've uncovered several issues with JSF 1.2 support. 1) The view root computes the next unique id differently, createUniqueId(). In the 1.1 version, the last generated sequence was not saved. Each time the view was restored the counter was reinitialized to zero. Under 1.2, the internal counter is restored. 2) The view root's UNIQUE_ID_PREFIX changed from id to j_id. This is used when generating unique id's. There is logic wired in the renderers that keys off the component id to determine if span tags should wrap the rendered markup. 3) JSP 1.2 has added a JspidComsumer that creates a unique id passed on to the component. JSP tags that implement this interfaces will always return the same id. The id is used to identify the corresponding component within the JSF component tree. This was added to allow dynamic changes to the structure of the component tree. 4) There are several component attributes that have been added. The view root and the label are a couple. 5) The dispatching logic from-view-id, to-view-id on a forward doesn't insist that the suffix of the request uri is changed to the javax.faces.DEFAULT_SUFFIX. So, if your target ends with ".faces", you end up in a infinite loop. You can argue that this is a stupid user trick anyway. It just behaves differently than 1.1. I've made a few changes addressing 1, 2, 3 and 5. The new clay configuration definitions need to be addressed. I'd like to find a way to generate these from the TLD. It sounded like Hermod Opstvedt had interest in created a maven mojo to handle this. I'm going to leave this ticket open to report on JSF 1.2 support as it progresses. BTW, Ryan, Glassfish rocks! > Clay examples from usecases demo output Sun's state field marker > ---------------------------------------------------------------- > > Key: SHALE-67 > URL: http://issues.apache.org/struts/browse/SHALE-67 > Project: Shale > Issue Type: Bug > Components: Clay > Environment: Operating System: All > Platform: All > Reporter: Ryan Lubke > > 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. -- 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
