I'd add a new option to the inputCalendar. Allow direct entry or so?
If you program that, Yee, I'll commit it. promised. regards, Martin On 3/28/06, Gerald Müllan <[EMAIL PROTECTED]> wrote: > On the other way, you can do a quickfix in case of this inputCalendar use > case; > > As Yura said, you can take a inputHidden and with some js coding on > every onchange event (to the readonly inputCalendar) push the date > value to the hidden element. > > Maybe a hidden inputCalender too, instead of the "normal" inputHidden, > and of course the value must be bound to the same model value (sure :) > ) > > As mentioned, the hidden value will be posted to server. > > regards, > > Gerald > > On 3/7/06, Yee CN <[EMAIL PROTECTED]> wrote: > > > > > > > > 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 > > > > > > > -- > Gerald Müllan > Schelleingasse 2/11 > 1040 Vienna, Austria > 0043 699 11772506 > [EMAIL PROTECTED] > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
