Why we have 2 different things now because it was already 2 different things in the code base
By default nullValid was "" and null was "Choose One"
And we couldn't distinguish between them at all but the are different. Especially now we wanted
those default messages out of the code and into a property file...
johan
On 4/19/06, Gustavo Hexsel <[EMAIL PROTECTED]> wrote:
Still on the "properties suffixes" saga:
The process for determining suffixes 'null' and 'nullValid' seems to have changed. Until 1.2b3, the loader would try to load the component name (without the hierarchy) followed by 'null'. For instance, for my list component, named "site", that contains dropdownchoices, the properties name for the null value was:
site.null=Please select a site
On 1.2rc1, the process seems to be using the hierarchy, which causes the prefix to include the listitem index. I've stepped through the code, and it seems to be looking for:
form.authenticationPanel.loginType.passwordSupportedDiv.siteLoginList.0.site.nullValid
which is impossible to use as I have a variable number of entries on the page. Is there a work-around?
Also, is there a compelling reason for have 'null' and 'nullValid' suffixes? It broke a bunch of pages for a corner-case which I can't even imagine (same component being mandatory sometimes and sometimes not, and needing different messages on each case???).
[]s Gus
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
