Hmm. That seems like a really good way to handle this, but I looked through
all of the documentation on tr:commandButton and couldn't find anything like
that. Maybe trinidad doesn't support this?
--- Mike Kienenberger [EMAIL PROTECTED] wrote:
To do this with the Tomahawk subForm, you'd use actionFor=subFormA
and you'd give the SubForm for A an id of subFormA. I think the
same method works for Trinidad, but the attribute name for
tr:commandButton might be different.
On 4/19/07, D. Cardon [EMAIL PROTECTED] wrote:
Hi,
I have two compound components, A and B, which need to be validated
separately.
So, I've placed each in its own subform. Outside of these components, I
have
a 'submit' button, like this:
tr:form
!-- Component A --
tr:subform
tr:inputText value=#{backBean.itemName} required=true /
/tr:subform
!-- Component B --
tr:subform default=true
tr:inputText value=#{backBean.entry} autoSubmit=true
validator=#{backBean.entryValidator} /
/tr:subform
!-- Submit Button --
tr:commandButton text=Submit action=#{backBean.submit} /
/tr:form
Component B uses PPR and does its own validation correctly, but component A
does not and should be validated when the submit button is pressed.
However,
since the submit button does not reside inside of component A's subform, A
is
not validated and invalid data may be sent when the submit button is
pressed.
If I move A outside of its subform (so it's at the form level), then
changing
values in B results in the premature validation of A, which I don't want.
How can I get A's validation to fire when the submit button is pressed?
Thanks,
--David
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
