XPages

In the previous part I created a ListPicker class that extends IValuePickerData and Serializable. The hasCapability() and getSourceLabels() methods that the IValuePickerData interface requires have been implemented and just return false. In addition to the default constructor public ListPicker(), I’ve created two more: public ListPicker(List<String>) and public ListPicker(Set<String>). Because I’ve just used the generic classes

So we’ve added our Value Picker to the XPage, bound the component to an Edit Box or Dojo List Text Box or some other control that’s bound to a field on a Notes Document or viewScope variable. Now we’re ready to go. A dataProvider for a Value Picker needs to implement the Java class com.ibm.xsp.extlib.component.picker.data.IValuePickerData (implement

The Extension Library brings a new control to the party, the Value Picker. This gives the user an image or link that spawns a dialog from which they can select one or more options and even search for options. (The Value Picker itself doesn’t differentiate whether or not multiple items can be selected. That’s handled

Ok. So we’ve seen we can pass a Vector or an ArrayList into a selectItems control for a Combo Box or Radio Button. And we’ve seen we can pass it via SSJS or EL (but EL is slightly more efficient). That’s all well and good if your options are already unique and already sorted. But

So enough of the introduction, onto passing some Java to selectors. There are two types of Collections you may have – Lists and Maps. Lists just have values. Maps have keys and values. So if you want the label and the value to be the same, use a List. If you want a different label

It’s no surprise that, despite coming from a background of minimal Java in the days before XPages, I now use Java as my main language in XPages back-end coding. There are a few areas where I’ve had to put my thinking cap on to work out how to use Java correctly when mapping between components