I've just updated an app from 4.0.2 to 4.1.2-SNAPSHOT, current as of
Feb 23rd, and can confirm that this is still a problem.
Previously (in 4.0.2) if you left a text field (say it was a score)
empty, the field would take on the value of 0 (can't imagine why you
would ever want this, but that's what it does).
If you set the omitZero parameter on the NumberTranslator on this
field to true, then, it would remain null (desired behaviour) when
empty.
In 4.1.2-SNAPSHOT, it always converts to 0, regardless of the value
of the omitZero parameter (bad).
J
On 8-Jan-07, at 9:56 AM, Jesse Kuhnert wrote:
This was a jira issue "fixed" recently. I'm not sure I understand what
the expected->actual results are that are questionable.
On 1/8/07, Patrick Klein <[EMAIL PROTECTED]> wrote:
Hi!
After a little testing:
The behaviour of the NumberTranslater is persistent in version 4.1.1.
Switching back to 4.0.2 for now, which is nothing i want to do as i'd
like to use the ajax functionality of tap 4.1.x ...
Regards,
Patrick
> Hi!
>
> I just recognized that the NumberTranslator does not seem to work
> correctly. OmitZero=true results in no value shown in the form-
field
> after a rewind but the value "0" is stored inside the corresponding
> Long- (or Integer / BigDecimal / ...) variable. OmitZero=false
shows
> the stored "0" in the form-field.
>
> Has anyone recognized this behaviour, too and if yes is there a
> workaround (except writing your own NumberTranslator)? Or is this
> Problem maybe allready known and fixed...?
>
> I'm using this mornings (GMT+1) Tapestry 4.1.2 Snapshot from
> mvn-snapshot.
>
> Regards,
> Patrick
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
