: Montag, 22. Oktober 2007 17:47
To: MyFaces Discussion
Subject: Re: optional validator - missing rendered attribute
For what it's worth, the optional validation discussions of the past
dealt with wrapping each validator in an optional validator
component, and then globally traversing
with session scoped beans ?
Michael
-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent: Montag, 22. Oktober 2007 17:47
To: MyFaces Discussion
Subject: Re: optional validator - missing rendered attribute
For what it's worth, the optional
: Re: optional validator - missing rendered attribute
For what it's worth, the optional validation discussions of the past
dealt with wrapping each validator in an optional validator
component, and then globally traversing the component tree. This
approach works very poorly, so I
Subject: Re: optional validator - missing rendered attribute
Hi Michael,
This requirement does sound a bit odd to me. To me, the primary role for
a validator is to determine whether the data is safe to push into the
model. Why would you want to bypass that kind of check in any
circumstance
Michael Heinen [EMAIL PROTECTED] schrieb:
A simple example is the dynamic rendering of range input fields.
A validator should be added only to the second field (e.g. dateTo or a
max size) which validates the lower value and the upper value.
Sorry, I don't understand that at all.
Or some
?
Michael
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Montag, 22. Oktober 2007 13:43
To: MyFaces Discussion
Cc: Michael Heinen
Subject: RE: optional validator - missing rendered attribute
Michael Heinen [EMAIL PROTECTED] schrieb:
A simple example is the dynamic
Hi Michael,
Michael Heinen [EMAIL PROTECTED] schrieb:
Here is a sample:
t:dataList id=myFields
value=#{FieldConfigurationController.myFields}
var=entry
t:div rendered=#{entry.type=='inputText'}
t:inputText id=s_inputText
Kitching [mailto:[EMAIL PROTECTED]
Sent: Montag, 22. Oktober 2007 16:08
To: MyFaces Discussion
Cc: Michael Heinen
Subject: RE: optional validator - missing rendered attribute
Hi Michael,
Michael Heinen [EMAIL PROTECTED] schrieb:
Here is a sample:
t:dataList id=myFields
value
a
container tag rather than directly a field.
Michael
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Montag, 22. Oktober 2007 16:08
To: MyFaces Discussion
Cc: Michael Heinen
Subject: RE: optional validator - missing rendered attribute
Hi Michael,
Michael
?
Michael
-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent: Montag, 22. Oktober 2007 17:47
To: MyFaces Discussion
Subject: Re: optional validator - missing rendered attribute
For what it's worth, the optional validation discussions of the past
dealt with wrapping
. Oktober 2007 17:47
To: MyFaces Discussion
Subject: Re: optional validator - missing rendered attribute
For what it's worth, the optional validation discussions of the past
dealt with wrapping each validator in an optional validator
component, and then globally traversing the component tree
Hi Michael,
This requirement does sound a bit odd to me. To me, the primary role for
a validator is to determine whether the data is safe to push into the
model. Why would you want to bypass that kind of check in any
circumstance?
Regards,
Simon
On Fri, 2007-10-19 at 10:51 -0400, Simon Lessard
Hello Michael,
You could add the check directly inside the validate method to see if the
validation should occur or not. Also since validators aren't visual
artifacts, rendered would not be very semantically correct. However, I guess
a relevant or active attribute could have been considered, but
Is there any reason why validators don't have a rendered attribute?
I use a dataList to render a List of fields dynamically and want to add
a validator to an input field depending on an EL expression.
I found some old discussions in the list about optional validators but
did not find detailed
14 matches
Mail list logo
