y users
Sent: Tuesday, January 01, 2013 8:19 AM
Subject: Re: select blankOption
Agreed. To avoid thinking about the sequence of getters, set up the form in
onPrepareForRender().
Eg.
http://jumpstart.doublenegative.com.au/jumpstart/examples/select/easyobject
As for the ValueEncoder
eEncoder which has to invoke the
>>> DAO again to obtain a matching user although these were already loaded up
>>> when the model was created. It would be nice if the model cached the users
>>> and simply referred back to them there.
>>>
>>> public Use
; and simply referred back to them there.
>>
>>public UserBean toValue(String clientValue) {
>> try {
>> return usersDAO.getUser(Integer.parseInt(clientValue));
>> } catch (Exception ex) {
>> log.error("user encoder could not
> return null;
> }
> }
>
> So overall I see the need for some shared cache with the select component,
> just loading a map up should do it?
>
> John
> - Original Message -
> From: Geoff Callender
> To: Tapestry users
> Sent: Sunda
inal Message -
From: Geoff Callender
To: Tapestry users
Sent: Sunday, December 30, 2012 3:00 PM
Subject: Re: select blankOption
Some code please.
On 31/12/2012, at 1:42 AM, John wrote:
> I got that to work, it's great, I hadn't notice all the values can have a
pr
been using
> intermediate helper beans to bind the related state data.
>
> John
> - Original Message -
> From: Geoff Callender
> To: Tapestry users
> Sent: Sunday, December 30, 2012 1:37 PM
> Subject: Re: select blankOption
>
>
> Ah, so yo
To: Tapestry users
Sent: Sunday, December 30, 2012 1:37 PM
Subject: Re: select blankOption
Ah, so you were. Same applies.
On 31/12/2012, at 12:24 AM, John wrote:
> I was talking about blankOption, but I'll try with the prop prefix.
> - Original Message -
Ah, so you were. Same applies.
On 31/12/2012, at 12:24 AM, John wrote:
> I was talking about blankOption, but I'll try with the prop prefix.
> - Original Message -
> From: Geoff Callender
> To: Tapestry users
> Sent: Sunday, December 30, 2012 12:16 PM
&g
I was talking about blankOption, but I'll try with the prop prefix.
- Original Message -
From: Geoff Callender
To: Tapestry users
Sent: Sunday, December 30, 2012 12:16 PM
Subject: Re: select blankOption
The default prefix is "literal". Use "pr
The default prefix is "literal". Use "prop", eg. blankLabel="prop:yourProperty".
See Binding Expressions in http://tapestry.apache.org/component-parameters.html
.
Cheers,
Geoff
On 30/12/2012, at 11:07 PM, John wrote:
> I would like to choose dynamically whether to display the blank option in
I would like to choose dynamically whether to display the blank option in my
select component.
I am using it to display an ALL value and don't want to show this if the select
has only 1 option.
Unfortunately the docs say that the blankOption is a literal and not a
property. Is there any way to
11 matches
Mail list logo
