You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Gianni Doe <gd...@yahoo.it> on 2009/04/06 11:59:39 UTC
Re: validation message-keys differences on m3 to rc2
ComponentStringResourceLoader's javadoc is very helpful here:
<quote>
assume a component hierarchy like page1.form1.input1 and your are
requesting a key named 'Required'. Wicket will search the property in
the following order:
page1.properties => form1.input1.Required
page1.properties => Required
form1.properties => input1.Required
form1.properties => Required
input1.properties => Required
myApplication.properties => page1.form1.input1.Required
myApplication.properties => Required
</quote>
What it doesn't mention is that if the form component is nested in
another container such as a border then the border id needs to be
included in the key.
e.g. if I have page1.form1.border1.input1 then in the form's
properties file I have to include the border component in the key -
border1.input1.Required, it would be cleaner just to be able to use
input1.Required.
-Gianni
On 18/mar/09, at 21:09, Gianni Doe wrote:
> https://issues.apache.org/jira/browse/WICKET-2159
>
> On 10/mar/09, at 15:55, Igor Vaynberg wrote:
>
>> jira, quickstart, you know the drill
>>
>> -igor
>>
>> On Tue, Mar 10, 2009 at 3:15 AM, gilberthuph <gd...@yahoo.it>
>> wrote:
>>>
>>> I'm having exactly the same problem after moving from 1.4-rc1 ->
>>> 1.4-rc2
>>>
>>> Here's the extract from my properties file TaxiBookingPage.xml.
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/
>>> properties.dtd">
>>> <properties>
>>> <entry
>>> key="generalDetails.numberOfVehiclesRequired.Required">You must
>>> enter the number of vehicles</entry>
>>> .. snip ..
>>> </properties>
>>>
>>> RC1
>>> ========================
>>> The key "generalDetails.numberOfVehiclesRequired.Required" is found
>>> immediately and the appropriate message retrieved.
>>>
>>> 11:00:38.595 [http-8180-3] DEBUG org.apache.wicket.Session -
>>> Getting
>>> page [path = 4:taxiBookingForm, versionNumber = 0]
>>> 11:00:38.609 [http-8180-3] DEBUG
>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>> Found
>>> resource from: com/rp/webapp/taxi/TaxiBookingPage.; key:
>>> generalDetails.numberOfVehiclesRequired.Required
>>>
>>>
>>> RC2
>>> ========================
>>> Does not attempt to look up
>>> "generalDetails.numberOfVehiclesRequired.Required" but the key
>>> "taxiBookingForm
>>> .numberOfVehiclesContainer
>>> .numberOfVehiclesRequiredBorder
>>> .generalDetails.numberOfVehiclesRequired.Required"
>>> which is not found.
>>>
>>> 10:47:47.902 [http-8180-1] DEBUG org.apache.wicket.Localizer -
>>> Locate
>>> property: key: 'Required'; Component: '[MarkupContainer [Component
>>> id =
>>> generalDetails.numberOfVehiclesRequired]]'
>>> 10:47:47.903 [http-8180-1] DEBUG
>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>> component:
>>> '[MarkupContainer [Component id =
>>> generalDetails.numberOfVehiclesRequired]]'; key: 'Required'
>>> 10:47:47.903 [http-8180-1] DEBUG
>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>> key:
>>> 'taxiBookingForm
>>> .numberOfVehiclesContainer
>>> .numberOfVehiclesRequiredBorder
>>> .generalDetails.numberOfVehiclesRequired.Required';
>>> class: 'com.rp.webapp.taxi.TaxiBookingPage'; locale: 'en_GB';
>>> Style: 'null'
>>> 10:47:47.903 [http-8180-1] DEBUG
>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>> Found
>>> properties file: 'com/rp/webapp/taxi/TaxiBookingPage.' but it
>>> doesn't
>>> contain the property
>>>
>>> So it seems the lookup algorithm hasn't changed but the message key.
>>>
>>> Is this a bug or should we now be using the full form-relative key
>>> as shown
>>> above?
>>>
>>>
>>>
>>> Alexander Lohse wrote:
>>>>
>>>> I could not find any reported changes concerning validation message
>>>> keys from version 1.4-m3 to 1.4-rc2, but I have the following
>>>> "required" key in my application resources that does not work
>>>> anymore.
>>>> .. trim ..
>>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/validation-message-keys-differences-on-m3-to-rc2-tp22155986p22431244.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: validation message-keys differences on m3 to rc2
Posted by Brill Pappin <br...@pappin.ca>.
I'm having a bit of trouble with this as well.
Are the properties document any place? I can't seem to find them
anywhere.
- brill
On 6-Apr-09, at 5:59 AM, Gianni Doe wrote:
> ComponentStringResourceLoader's javadoc is very helpful here:
>
> <quote>
> assume a component hierarchy like page1.form1.input1 and your are
> requesting a key named 'Required'. Wicket will search the property
> in the following order:
>
> page1.properties => form1.input1.Required
> page1.properties => Required
> form1.properties => input1.Required
> form1.properties => Required
> input1.properties => Required
> myApplication.properties => page1.form1.input1.Required
> myApplication.properties => Required
> </quote>
>
> What it doesn't mention is that if the form component is nested in
> another container such as a border then the border id needs to be
> included in the key.
>
> e.g. if I have page1.form1.border1.input1 then in the form's
> properties file I have to include the border component in the key -
> border1.input1.Required, it would be cleaner just to be able to use
> input1.Required.
>
> -Gianni
>
>
>
> On 18/mar/09, at 21:09, Gianni Doe wrote:
>
>> https://issues.apache.org/jira/browse/WICKET-2159
>>
>> On 10/mar/09, at 15:55, Igor Vaynberg wrote:
>>
>>> jira, quickstart, you know the drill
>>>
>>> -igor
>>>
>>> On Tue, Mar 10, 2009 at 3:15 AM, gilberthuph <gd...@yahoo.it>
>>> wrote:
>>>>
>>>> I'm having exactly the same problem after moving from 1.4-rc1 ->
>>>> 1.4-rc2
>>>>
>>>> Here's the extract from my properties file TaxiBookingPage.xml.
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/
>>>> properties.dtd">
>>>> <properties>
>>>> <entry
>>>> key="generalDetails.numberOfVehiclesRequired.Required">You must
>>>> enter the number of vehicles</entry>
>>>> .. snip ..
>>>> </properties>
>>>>
>>>> RC1
>>>> ========================
>>>> The key "generalDetails.numberOfVehiclesRequired.Required" is found
>>>> immediately and the appropriate message retrieved.
>>>>
>>>> 11:00:38.595 [http-8180-3] DEBUG org.apache.wicket.Session -
>>>> Getting
>>>> page [path = 4:taxiBookingForm, versionNumber = 0]
>>>> 11:00:38.609 [http-8180-3] DEBUG
>>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>>> Found
>>>> resource from: com/rp/webapp/taxi/TaxiBookingPage.; key:
>>>> generalDetails.numberOfVehiclesRequired.Required
>>>>
>>>>
>>>> RC2
>>>> ========================
>>>> Does not attempt to look up
>>>> "generalDetails.numberOfVehiclesRequired.Required" but the key
>>>> "taxiBookingForm
>>>> .numberOfVehiclesContainer
>>>> .numberOfVehiclesRequiredBorder
>>>> .generalDetails.numberOfVehiclesRequired.Required"
>>>> which is not found.
>>>>
>>>> 10:47:47.902 [http-8180-1] DEBUG org.apache.wicket.Localizer
>>>> - Locate
>>>> property: key: 'Required'; Component: '[MarkupContainer
>>>> [Component id =
>>>> generalDetails.numberOfVehiclesRequired]]'
>>>> 10:47:47.903 [http-8180-1] DEBUG
>>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>>> component:
>>>> '[MarkupContainer [Component id =
>>>> generalDetails.numberOfVehiclesRequired]]'; key: 'Required'
>>>> 10:47:47.903 [http-8180-1] DEBUG
>>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>>> key:
>>>> 'taxiBookingForm
>>>> .numberOfVehiclesContainer
>>>> .numberOfVehiclesRequiredBorder
>>>> .generalDetails.numberOfVehiclesRequired.Required';
>>>> class: 'com.rp.webapp.taxi.TaxiBookingPage'; locale: 'en_GB';
>>>> Style: 'null'
>>>> 10:47:47.903 [http-8180-1] DEBUG
>>>> org.apache.wicket.resource.loader.ComponentStringResourceLoader -
>>>> Found
>>>> properties file: 'com/rp/webapp/taxi/TaxiBookingPage.' but it
>>>> doesn't
>>>> contain the property
>>>>
>>>> So it seems the lookup algorithm hasn't changed but the message
>>>> key.
>>>>
>>>> Is this a bug or should we now be using the full form-relative
>>>> key as shown
>>>> above?
>>>>
>>>>
>>>>
>>>> Alexander Lohse wrote:
>>>>>
>>>>> I could not find any reported changes concerning validation
>>>>> message
>>>>> keys from version 1.4-m3 to 1.4-rc2, but I have the following
>>>>> "required" key in my application resources that does not work
>>>>> anymore.
>>>>> .. trim ..
>>>>>
>>>>
>>>> --
>>>> View this message in context: http://www.nabble.com/validation-message-keys-differences-on-m3-to-rc2-tp22155986p22431244.html
>>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>