Apache Tapestry and Custom Components: DateInput - Creating the Models (
Page 3 of 5 )
As you already know pretty well, we have to give PropertySelection components their models, explaining to them what exactly to display and what to return to the page class when the user makes a selection. The model for days is very simple and can be implemented in a few different ways. Here is one of the options:
public class DayModel implements IPropertySelectionModel {
public String getLabel(int index) {
return "" + (index + 1);
}
public Object getOption(int index) {
return index + 1;
}
public int getOptionCount() {
return 31;
}
public String getValue(int index) {
return "" + index;
}
public Object translateValue(String value) {
return Integer.parseInt(value) + 1;
}
}
We are simply displaying numbers from 1 to 31 as labels and use the indexes of the options for value attributes. I don’t feel like any explanations are needed here, but if you do have a question, please ask it at the discussions page. In any case, reviewing the article devoted to IPropertySelectionModel might be useful.
The model for selecting a year is also quite simple:
public class YearModel implements IPropertySelectionModel {
private final static int START_YEAR = 1900;
private final static int END_YEAR =
new GregorianCalendar().get(Calendar.YEAR);
public String getLabel(int index) {
return Integer.toString(index + START_YEAR);
}
public Object getOption(int index) {
return index + START_YEAR;
}
public int getOptionCount() {
return END_YEAR - START_YEAR + 1;
}
public String getValue(int index) {
return "" + index;
}
public Object translateValue(String value) {
return Integer.parseInt(value) + START_YEAR;
}
}
Everything should be more or less clear to you here, or if not, welcome to the discussions page. The model for months is slightly more interesting because it returns months’ names using the existing locality settings. For example, they will be automatically displayed in Spanish if your preferred language is Spanish, etc. This means that DateInput can be very easily localized, and we shall discuss this in more detail in a coming article on internationalization. For now, just have a look at the code and, of course, add this class to your application:
public class LocalisedMonthsModel implements IPropertySelectionModel {
private String[] months;
public LocalisedMonthsModel(Locale locale) {
DateFormatSymbols symbols = new DateFormatSymbols(locale);
months = symbols.getMonths();
}
public String getLabel(int index) {
return months[index];
}
public Object getOption(int index) {
return index;
}
public int getOptionCount() {
return 12;
}
public String getValue(int index) {
return "" + index;
}
public Object translateValue(String value) {
return Integer.parseInt(value);
}
}
 |
