[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] Mike Kienenberger updated TOMAHAWK-134: --- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] updated TOMAHAWK-134: -- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] Mike Kienenberger updated TOMAHAWK-134: --- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] updated TOMAHAWK-134: -- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] Mike Kienenberger updated TOMAHAWK-134: --- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-134) t:saveState only works with client-side state saving
[ http://issues.apache.org/jira/browse/TOMAHAWK-134?page=all ] updated TOMAHAWK-134: -- > t:saveState only works with client-side state saving > > > Key: TOMAHAWK-134 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-134 > Project: MyFaces Tomahawk > Type: Bug > Components: UISaveState > Environment: Windows XP, RSA 6.0.1, JDK 1.5.0_04, Tomcat 5.0.28, Sun RI > (distributed with RSA 6.0.1), Tomahawk nightly build (17/10/05) > Reporter: Juan Medín > > t:saveState doesn't store the state when setting STATE_SAVING_METHOD to > server. It _does_ work when setting STATE_SAVING_METHOD to client. > I'm using the Sun RI (distributed with RSA 6.0.1) plus a recent nightly build > of Tomahawk. > The test code is trivial: two JSPs with value="aRequestScopedObject"/> like this: > > > > > more html > The generated HTML doesn't include any reference to the saveState object when > setting server-side state saving. For the example above in a simple test form > with two fields (text1 and text2) this is the generated form code: > action="/testbox/faces/app/savestate/test1.jsp" >enctype="application/x-www-form-urlencoded"> >name="form1:text1" value=""/> >name="form1:text2" value=""/> >name="form1:button1" id="form1:button1"/> > > > There is no html code for the saveState() tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
