Hi!
How about keepSubmittedValues which is a bit more specific than
keepInput?
However, it doesn't matter too much what we call it.
t:dataTable has something called preserveRowStates which has a
similar purpose, but I can't see how we can use the same name (nor am
I sure that
That's probably good enough. Keeps the preserve theme we've used
up to this point and accurately states what's preserved.
On 5/25/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
How about keepSubmittedValues which is a bit more specific than
keepInput?
However, it doesn't matter too
Hi!
It looks like model changes are not reflected in subforms not subject of
the current request.
So if you have stuff like:
h:form
h:commandInput /
h:commandButton id=btn1 /
s:subForm
h:selectOneMenu /
h:commandButton id=btn2 /
/s:subForm
This is how subforms are supposed to work -- changes and submits in
one subform should not impact the current submitted values of the
others.
If you want to change the submitted values to the backing bean, then
you need to do so in code just as if you wanted to do it for a regular
form.
Hi Mike!
If you want to change the submitted values to the backing bean, then
you need to do so in code just as if you wanted to do it for a regular
form.
http://wiki.apache.org/myfaces/ClearInputComponents
Yep, I am aware of this, but I really hate to use component bindings.
This is alway a
No, the main goal of subform was to allow you to submit and validate
part of a page without affecting the rest of the page.
Perhaps for your own use cases, you've primarily used it to do partial
page refreshing, but that's not how I've used it. I would disagree
that this is the majority use
Hi !
One of my primary use cases is to do something like
set of input field rows
add-new-row button inside of a subForm
This means you allow the user to add some rows and validate the input at
a later save point at once?
However, you won :-)
So I'll try to develop the attribute with a
How about keepSubmittedValues which is a bit more specific than keepInput?
However, it doesn't matter too much what we call it.
t:dataTable has something called preserveRowStates which has a
similar purpose, but I can't see how we can use the same name (nor am
I sure that preserveRowStates is
