On Thu, 30 Apr 2015 12:58:23 -0300, Lance Java
wrote:
If you want tapestry to use your translator as the default for all dates
you should contribute to TranslatorSource using a class (instead of
contributing by name to TranslatorAlternativesSource).
Otherwise, you could annotate individual d
If you want tapestry to use your translator as the default for all dates
you should contribute to TranslatorSource using a class (instead of
contributing by name to TranslatorAlternativesSource).
Otherwise, you could annotate individual date fields with
@Translate("dateTranslator") and leave your
I have implemented a simple Translator for dates, but I am at a loss trying to
understand why I get a RenderQueueException "Parameter 'translate' of component
XXX is bound to null. This parameter is not allowed to be null" while actually
the TextField component mentioned in that exception certai
Very interesting, I will definitely explore this possibility.
-Original Message-
From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Thursday, April 30, 2015 15:23
To: Tapestry users
Subject: Re: Customized display/edit blocks for components other than the grid
On Thu,
On Thu, 30 Apr 2015 08:35:05 -0300, Davide Vecchi wrote:
Ok, thanks for the explanation. Right now we can't update to 5.4 but
when we do we will explore the possibility you mentioned. For now we
have just slightly changed our requirements and we can use the Tapestry
Translator to achieve w
Are you aware that BeanEditor, BeanEditForm and BeanDisplay all obey the
BeanBlockSource?
Ok, thanks for the explanation. Right now we can't update to 5.4 but when we do
we will explore the possibility you mentioned. For now we have just slightly
changed our requirements and we can use the Tapestry Translator to achieve what
we need.
Thanks for the quick assistance as usual.
-O
Great, thank you!
2015-04-30 12:16 GMT+02:00 Dimitris Zenios :
> Also you dont need to build by hand.You can get it from apache staging repo
>
>
> apache-staging
> https://repository.apache.org/content/groups/staging/
>
>
>
> On Thu, Apr 30, 2015 at 1:16
Also you dont need to build by hand.You can get it from apache staging repo
apache-staging
https://repository.apache.org/content/groups/staging/
On Thu, Apr 30, 2015 at 1:16 PM, Dimitris Zenios
wrote:
> There was also a bug for this
> https://issues.apa
There was also a bug for this
https://issues.apache.org/jira/browse/TAP5-2391
so please close your bug since its a duplicate and already fixed
Dimitris Zenios
On Thu, Apr 30, 2015 at 1:14 PM, Nicolas Bouillon
wrote:
> Indeed, i've built the latest beta tag (5.4-beta-31) and the bug is
> correc
Indeed, i've built the latest beta tag (5.4-beta-31) and the bug is
corrected.
Thanks
2015-04-30 11:40 GMT+02:00 Nicolas Bouillon :
> I'm using the lastest in maven central, 5.4-beta-26
>
> 2015-04-30 11:17 GMT+02:00 Dimitris Zenios :
>
>> This has been fixed in the latest snapshot.What version
I'm using the lastest in maven central, 5.4-beta-26
2015-04-30 11:17 GMT+02:00 Dimitris Zenios :
> This has been fixed in the latest snapshot.What version of 5.4 are you
> using?
>
> On Thu, Apr 30, 2015 at 11:49 AM, Nicolas Bouillon
> wrote:
>
> > I know the same field component is reused. I ha
This has been fixed in the latest snapshot.What version of 5.4 are you
using?
On Thu, Apr 30, 2015 at 11:49 AM, Nicolas Bouillon
wrote:
> I know the same field component is reused. I have used this kind of
> structures (field in loop) extensively in a previous project on Tapestry
> 5.3 without a
I know the same field component is reused. I have used this kind of
structures (field in loop) extensively in a previous project on Tapestry
5.3 without any problems. That's for sure a regression between 5.3 and 5.4,
probably caused by the removal of the redirection after validation failure
in a fo
The problem is that the same field is reused for each loop iteration. See
here for a workaround using a FieldSnapshot to record the errors.
http://t5stitch-lazan.rhcloud.com/mapbindingdemo
Hi,
I've got an issue with a form containing a loop which contains text fields.
When the validation fails server side, the page is supposed to be
re-rendered with the incorrect values filled in. But in this case, the
field which is repeated will be filled with the last value entered in the
repeat
16 matches
Mail list logo