You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Yee CN <ye...@streamyx.com> on 2006/03/07 10:32:29 UTC
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
[SPAM] Re: readonly entities no longer pass value back to backing bean?
Posted by Yee CN <ye...@streamyx.com>.
Sorry Martin - been overwhelmed with project deadline, so won't have time to
contribute anything in the near future. Hope somebody get this sorted out
soon.
I am thinking - there is a disabled property, and that is actually being
used in our usual 'readonly' sense. Then there is the readonly property,
which to me is meaningless and downright wrong in the context of
t:inputCalendar.
The situation is quite confusing really, and the crux of the matter being
that the behavior of html elements got mixed up with the behavior of JSF
components. It also affect other components like t:selectOneMenu and
t:selectBooleanCheckBox, although not as severely as t:inputCalendar
Does anybody has any suggestions on how to sort this out once and for all?
Regards,
Yee
-----Original Message-----
From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
Sent: Wednesday, 29 March 2006 2:04 AM
To: MyFaces Discussion
Subject: [SPAM] Re: readonly entities no longer pass value back to backing
bean?
Importance: Low
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 <bi...@gmail.com> 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 <ye...@streamyx.com> 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
> Bierbrauen@gmail.com
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: readonly entities no longer pass value back to backing bean?
Posted by Martin Marinschek <ma...@gmail.com>.
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 <bi...@gmail.com> 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 <ye...@streamyx.com> 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
> Bierbrauen@gmail.com
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: readonly entities no longer pass value back to backing bean?
Posted by Gerald Müllan <bi...@gmail.com>.
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 <ye...@streamyx.com> 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
Bierbrauen@gmail.com
Re: readonly entities no longer pass value back to backing bean?
Posted by Gerald Müllan <bi...@gmail.com>.
Hi,
don`t know if this also meets your requirements, but you can set
disabledOnClientSide="true", the field will be disabled and you can be
sure that the values will be posted back to server.
But as far as i know, this attribute exists only on t:inputText.
regards,
Gerald
On 3/7/06, Yee CN <ye...@streamyx.com> 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
Bierbrauen@gmail.com
[SPAM] Re: readonly entities no longer pass value back to backing bean?
Posted by Yee CN <ye...@streamyx.com>.
That's makes a lot of sense. But it is ARRAGH nevertheless - as I have quite
a lot of readonly textboxes that are passing back values. t:inputCalender is
one single major offender, there are also some javascirpt calculated values.
Is there an elegant solution for inputCalendar? I really what to force users
to select from the popup calendar. Maybe make inputCalendar a special case?
Thanks
Yee
-----Original Message-----
From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
Sent: Tuesday, 28 March 2006 10:42 PM
To: MyFaces Discussion; yeecn@streamyx.com
Subject: [SPAM] Re: readonly entities no longer pass value back to backing
bean?
Importance: Low
Well, we're not supposed to take back the value when readonly=true.
That's as such in the spec.
regards,
Martin
On 3/28/06, Yee CN <ye...@streamyx.com> wrote:
> I tried the build from yesterday and still find the bug there - so I am
> still stuck with the build from early Feb. Is this bug meant to be fixed?
>
> Regards,
> Yee
>
> -----Original Message-----
> From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
> Sent: Wednesday, 8 March 2006 4:09 PM
> To: MyFaces Discussion; yeecn@streamyx.com
> Subject: Re: readonly entities no longer pass value back to backing bean?
>
> 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 <ye...@streamyx.com> 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:yeecn@streamyx.com]
> > 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
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
RE: readonly entities no longer pass value back to backing bean?
Posted by Yu...@muranosoft.com.
Hi, All
About <t:inputText id="totalAmount" value="myBean.totalAmount"
readonly="true"/>
JSF renders this component into HTML as disabled. It's not JSF issue to pass
values into request only when control is enable. It's HTML form logic, if
you wish enable value of the component try this scenario:
<t:inputText id="totalAmount" value="#{myBean.totalAmount}"
readonly="true"/>
<t:inputHidden id="HiddentotalAmount" value="#{myBean.totalAmount}" />
Best wishes,
Yura.
-----Original Message-----
From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
Sent: Tuesday, March 28, 2006 5:42 PM
To: MyFaces Discussion; yeecn@streamyx.com
Subject: Re: readonly entities no longer pass value back to backing bean?
Well, we're not supposed to take back the value when readonly=true.
That's as such in the spec.
regards,
Martin
On 3/28/06, Yee CN <ye...@streamyx.com> wrote:
> I tried the build from yesterday and still find the bug there - so I am
> still stuck with the build from early Feb. Is this bug meant to be fixed?
>
> Regards,
> Yee
>
> -----Original Message-----
> From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
> Sent: Wednesday, 8 March 2006 4:09 PM
> To: MyFaces Discussion; yeecn@streamyx.com
> Subject: Re: readonly entities no longer pass value back to backing bean?
>
> 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 <ye...@streamyx.com> 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:yeecn@streamyx.com]
> > 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
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: readonly entities no longer pass value back to backing bean?
Posted by Martin Marinschek <ma...@gmail.com>.
Well, we're not supposed to take back the value when readonly=true.
That's as such in the spec.
regards,
Martin
On 3/28/06, Yee CN <ye...@streamyx.com> wrote:
> I tried the build from yesterday and still find the bug there - so I am
> still stuck with the build from early Feb. Is this bug meant to be fixed?
>
> Regards,
> Yee
>
> -----Original Message-----
> From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
> Sent: Wednesday, 8 March 2006 4:09 PM
> To: MyFaces Discussion; yeecn@streamyx.com
> Subject: Re: readonly entities no longer pass value back to backing bean?
>
> 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 <ye...@streamyx.com> 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:yeecn@streamyx.com]
> > 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
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
RE: readonly entities no longer pass value back to backing bean?
Posted by Yee CN <ye...@streamyx.com>.
I tried the build from yesterday and still find the bug there - so I am
still stuck with the build from early Feb. Is this bug meant to be fixed?
Regards,
Yee
-----Original Message-----
From: Martin Marinschek [mailto:martin.marinschek@gmail.com]
Sent: Wednesday, 8 March 2006 4:09 PM
To: MyFaces Discussion; yeecn@streamyx.com
Subject: Re: readonly entities no longer pass value back to backing bean?
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 <ye...@streamyx.com> 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:yeecn@streamyx.com]
> 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
Re: readonly entities no longer pass value back to backing bean?
Posted by Martin Marinschek <ma...@gmail.com>.
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 <ye...@streamyx.com> 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:yeecn@streamyx.com]
> 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
RE: readonly entities no longer pass value back to backing bean?
Posted by Yee CN <ye...@streamyx.com>.
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:yeecn@streamyx.com]
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