https://issues.apache.org/jira/browse/TAP5-1512
On Mon, Apr 25, 2011 at 12:15 PM, Adam Zimowski wrote:
> After more debugging, the problem seems to be with Tapestry's
> IdAllocator and how it generates client side id's for select
> components, particularly when Zone is updated.
>
> In this case,
After more debugging, the problem seems to be with Tapestry's
IdAllocator and how it generates client side id's for select
components, particularly when Zone is updated.
In this case, what happens is that every time I update zone while form
is in error, the ID of my select changes with incremented
Okay, now I am pretty sure this is a bug related to usage of
in 5.2.5. If I put (which I didn't have
before), the state required error shows up as expected. If I use
attached to state field, the error does not show.
It's like looking for a needle in a haystack.. lol. still could
appreciate
Quick update:
By debugging Select component I see that validation tracker correctly
records the error when I submit the blank option for state. The blank
option is submitted throug the following use case:
1. Select country and state (both have blank options therefore are
required), but leave othe
I'm sorry, I am on Tapestry 5.2.5 :-)
On Thu, Apr 21, 2011 at 10:19 AM, Adam Zimowski wrote:
> @Josh - When I debug Select in 5.2.4 (break on processSubmission(),
> line 166), selectedValue is blank which is expected. So select
> correctly submits without a value, it's just it seems that the
> va
@Josh - When I debug Select in 5.2.4 (break on processSubmission(),
line 166), selectedValue is blank which is expected. So select
correctly submits without a value, it's just it seems that the
validator does not recognize that select state was repopulated via
zone and consequently no value was sub
When you say "Validation kicks in" does this occur after a submit? If so,
is it possible that AddressUIBean is remembering the value that was present
when the submit occurred and then on the second submit it is getting set to
null again?
At the point when you would expect an error to occur, what
I don't have the time now to dive into this, but it sounds like the
select thinks it has a value when it's time to validate. Have you set
a breakpoint in the Select component to see what it thinks that value
is?
Josh
On Wed, Apr 20, 2011 at 1:36 PM, Adam Zimowski wrote:
> Nobody ran into this? I
Nobody ran into this? I have a feeling that I'm doing something wrong,
but then, I'm not sure either if Tapestry is just not working as
expected.
If I make the stateUpdateZone wrap entire form, then form is aware of
state value change. But I do not want to refresh entire form, all I
want to update
I have a typical address form with street, city zip textfields and two
dropdowns: country and state. The state dropdown is wrapped in a zone
so that when country is selected, states are populated:
All works okay, except for a test case my business analyst found which
I can't figure out.
You fil
10 matches
Mail list logo
