Duh, that was easy. Actually what I was looking for is
component1Id.null=Choose type
component2Id.null=Choose date
but thank you very much!
2008/5/21 Maurice Marrink <[EMAIL PROTECTED]>:
> In the properties file for your page do:
> component1Id.nullValid=Choose type
> component2Id.nullValid=Choose date
>
> Instead of just the id you can also include the (partial) path,
> working your way to the top from the component you are trying to use.
>
> Maurice
>
> On Wed, May 21, 2008 at 8:08 PM, Martin Makundi
> <[EMAIL PROTECTED]> wrote:
>> Hi!
>>
>> Does the Wicket localizer support overriding localization for each
>> component? This is what I have:
>>
>> add(new DropDownChoice(TYPE_PICKER, typeChoices));
>> add(new DropDownChoice(DATE_PICKER, dateChoices));
>>
>> I would like to localize the null choice differently. Now it reads
>> "Choose one" for both dropdowns.
>>
>> What I would like is for the TYPE_PICKER to dispay "Choose type" and
>> the DATE_PICKER to display "Choose date".
>>
>> Can this be overcome using xx.properties files or do I have to create
>> a dummy "un-selected" element? The AbstractSingleSelect class renders
>> null as follows:
>> if (Strings.isEmpty(option))
>> {
>> option = getLocalizer().getString("null", this, CHOOSE_ONE);
>> }
>>
>>
>> **
>> Martin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
