It is no requirement - just a "recommendation". I have seen the RI implementation, and that one is a little complicated (something out of the sun blueprints). I wonder why it is still that complicated with the security package in Java, but it is.
Do you know of any open source encryption implementation were something like this is already covered? regards, Martin On 10/5/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > Martin, > > Is encrypting the client-side state a JSF 1.2 requirement? I seem to > recall seeing it in the new spec ... I remember bringing that issue up > a long time ago on this list or the Sun forum. Nice to see that its > being implemented. > > I have a few ideas on that but not time at the moment. :-( > > sean > > On 10/5/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > Hi Sharath, > > > > you started out perfectly right - by sending in patches for problems > > you had in your own projects. > > > > If you keep on doing this, you will automatically grow to be a valued > > member of the MyFaces committer, and based on the ASF meritocracy > > rules you might as well be offered a committership. > > > > If you want to help out on a larger scale: there are two major issues > > we need to have solved in the moment: > > > > 1) encrypting the client side state - check out the JSF RI on > > dev.java.net to check out how they are doing this > > 2) storing away the server side state for a number of the last requests > > > > plus: there are a 104 bugs open, so choose your fight ;) > > > > regards, > > > > Martin > > > > On 10/5/05, sharath reddy <[EMAIL PROTECTED]> wrote: > > > Hi Martin, > > > > > > Thanks for applying my patch and closing out this > > > issue. BTW, I would like to help out with the myfaces > > > project - perhaps with the documentation? I saw the > > > 'help wanted' posted on the wiki by Sean. > > > > > > Where (and how) do I start? > > > > > > Regards, > > > Sharath > > > > > > > > > > Martin Marinschek closed MYFACES-428: > > > > ------------------------------------- > > > > > > > > Fix Version: Nightly > > > > Resolution: Fixed > > > > > > > > thanks to Sharath Reddy for his patch > > > > > > > > > InputDate(s) within dataTable submitting incorrect > > > > dates > > > > > > > > > > > > -------------------------------------------------------- > > > > > > > > > > Key: MYFACES-428 > > > > > URL: > > > > http://issues.apache.org/jira/browse/MYFACES-428 > > > > > Project: MyFaces > > > > > Type: Bug > > > > > Versions: 1.0.9m9 > > > > > Environment: JDK 1.4.2_08, win XP, Jetty 5 > > > > > Reporter: Colin Chalmers > > > > > Assignee: Martin Marinschek > > > > > Priority: Minor > > > > > Fix For: Nightly > > > > > Attachments: inputDate.zip, inputdate > > > > > > > > > > Using InputDate within a dataTable to accept > > > > birthDates of clients. The dates are rendered > > > > correctly on screen afterwhich one may select the > > > > individual dates. After submitting to server all > > > > date objects in the individual customer objects are > > > > set to the *last* date that was selected. > > > > > A workaround I'm using at the moment is to use > > > > inputText fields in conjunction with a date pattern > > > > which works correctly. > > > > > Using the InputDate out with the datatable to > > > > accept (for example) a departure date works no > > > > problem. > > > > > > > > -- > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > __________________________________ > > > Yahoo! Mail - PC Magazine Editors' Choice 2005 > > > http://mail.yahoo.com > > > > > > > > > -- > > > > http://www.irian.at > > Your JSF powerhouse - > > JSF Trainings in English and German > > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
