It's in this latter entry that you identify the class name of the OptionListSourceFactory and the name of the specific OptionListSource that applies to the field to which this entry is related. You define the validator once in the validator-rules.xml file, and then reference it as many times as you need for individual field validation in the validation.xml file.
My intent here was just to demonstrate that once you create a component for one purpose, you often find that there are other, equally valuable uses for your component, and I believe that we have accomplished that with the server-side validation alone.
Hopefully, I have accomplished my goal of demonstrating some practical applications of the concepts that I have been promoting, and as a side benefit, produced something of value to someone at the same time. That's about it for the code examples, but next time I do want to wrap things up by going back to the original concepts and doing a little review.
Jeff Chilton is Vice President of Fulfillment at Echo Technology Group, Inc., an IT consulting firm that specializes in enterprise-focused best practices. He can be reached at email@example.com.