et to zero.
> -Original Message-
> From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 14, 2007 10:11 PM
> To: Tapestry users
> Subject: Re: I'm missing something obvious
>
> Aha.
>
> So the only real difference between the demo page and you
Aha.
So the only real difference between the demo page and your configuration is
that you specified a pattern of "0". The demo pages use the more generic #
(as well as the default for the number translator).
If I remember correctly specifying something like "0" for the pattern forces
your input
I'm assuming that any value between 1 and 99 should work. I just
tried 1234 and it failed as does every other number I type in.
Playing w/ the page at opencomponentry that you linked below, the
validators seem to work fine which is why I can't figure out what's up.
I really think I must
Hmm doesn't seem to be conjuring up any eurekas for me currently. .
I wonder what the difference is between your field and the fields on the
Workbench form?
http://opencomponentry.com:8080/workbench/Home,$Border.pageLink.sdirect?sp=SFields
It has a similar setup but I can't see where the error
Sorry Jesse, I didn't realize this message didn't have the whole trail.
I have a simple input:
the tradeId property is nothing more than:
public abstract Integer getTradeId();
No matter what value I enter, valid or not, I alway get a dojo popup
with 3 errors, the input must be a
What issue exactly is it that you see?
If you could provide the exact text that is presented as the reason for the
error as well as what input you gave it to produce the error I can be more
helpful.
On 5/14/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
Grabbing today's latest build, I'm still see
Grabbing today's latest build, I'm still seeing the same dojo validation
issue. As a bonus, there is a new debug message:
DEBUG: EXPERIMENTAL: dojo.i18n.number -- Not yet ready for use. APIs
subject to change without notice.
Happy Monday!
Thanks in advance,
Tony Nelson
Tony Nelson wrote:
I hadn't noticed this before. Yes a fix will go out tonight.
On 5/11/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
Does that mean there is a fix floating around somewhere?
Thanks
Tony
[EMAIL PROTECTED] wrote:
> This is a regression, the JIRA issue is
>
> https://issues.apache.org/jira/browse/TA
Does that mean there is a fix floating around somewhere?
Thanks
Tony
[EMAIL PROTECTED] wrote:
This is a regression, the JIRA issue is
https://issues.apache.org/jira/browse/TAPESTRY-1071
-Original Message-
From: Tony Nelson [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 6
This is a regression, the JIRA issue is
https://issues.apache.org/jira/browse/TAPESTRY-1071
> -Original Message-
> From: Tony Nelson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 10, 2007 6:57 PM
> To: Tapestry users
> Subject: I'm missing something obvious
>
> I have a simple form t
Client side.. the nifty new dojo popup.
If I disable client side validation it works fine, and I will do that
for now.. but I'd really rather not.
Thanks again
Tony
Andreas Andreou wrote:
well... the code is correct... i even tried it myself!
So, what kind of validation error you get?
Clien
well... the code is correct... i even tried it myself!
So, what kind of validation error you get?
Client side? or server side? What happens if you disable javascript?
On 5/11/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
Sorry, I should have supplied that in my original e-mail.
public abstr
Sorry, I should have supplied that in my original e-mail.
public abstract Integer getTradeId();
Thanks again
Tony
Andreas Andreou wrote:
What's the type of tradeId ?
On 5/10/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
I have a simple form that includes this:
And no matter what legal
What's the type of tradeId ?
On 5/10/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
I have a simple form that includes this:
And no matter what legal numeric value I enter, I always get a
validation error.
Where is my typo? Because I certainly can't find it.
I'm using yesterdays 4.1.2 snapsh
14 matches
Mail list logo
