The Customizer template is nothing more than a plain JPanel. It does not really have the stuff in it to be useful for either a bean Customizer or a custom proped component.


There should really be two templates:

- a JPanel implementing Customizer which would sensibly implement these three methods (keep a local variable for the customized bean, and use a PropertyChangeSupport to make it easy to fire changes)

- a JPanel to be used as a custom proped component, which should maybe have a constructor taking a PropertyEditor subclass and keeping a copy of the proped so that setValue() can be used

The second makes most sense in a group template together with the PropertyEditorSupport template.

Also, the P.E.S. template ought to have commented-out code for common (re-)implementations of the methods, e.g. at least something implementing a tagged pulldown list of fixed choices.