Hmm.... there was a fix in MyFaces were the bug was that we wrongly used "readOnly" to check if the readonly attribute was set.
for security considerations, the JSF engine doesn't take over disabled or readOnly attributes to the server, it was a bug that we did. regards, Martin On 3/8/06, Yee CN <[EMAIL PROTECTED]> wrote: > > > > Is that me only? Did anybody else observed this problem? > > > > For me nightly build around Feb 12 is OK, nightly around feb 25 not OK, > currently nightly not OK. > > > > Can someone please indicate one way or another so I can know whether it is > the combination of stuffs I used that caused the problem? > > > > Many thanks in advance. > > Yee > > > > > > ________________________________ > > > From: Yee CN [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 7 March 2006 5:32 PM > To: 'MyFaces Discussion' > Subject: readonly entities no longer pass value back to backing bean? > > > > > Hi, > > > > I discovered the recent nightly builds has stop sending values back to the > backing bean when readonly attribute is set to true. For example: > > > > <t:inputText id="totalAmount" value="myBean.totalAmount" readonly="true" /> > > > > The totalAmount is meant to be a readonly textbox, whose value is calculated > via javascript. > > > > Another example is inputCalendar, where the date should only be selected > from the popup window, and now key in directly: > > > > <t:inputCalendar id="dateFrom" … readonly="true" /> > > > > > > I find that all of these entities will no longer pass the input box value to > the backing bean. I tested it with the build downloaded today and find it to > be so. I have a version downloaded around 10 Feb and that one was working > OK. > > > > Is this a bug? Or is this a design change? > > > > Thanks > > > > Yee > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
