Metacat

Instead of hard coding in each action into metacat, actions could be loaded
dynamically by defining a class which contains a method that executes the action
specified. This class would be modeled around another abstract class to define
the method name and any instance variables that would be needed. MetaCat would
then dynamically load the class to handle the action. The action->class mapping
could be handled by the xml_catalog table or by a properties file. This
implements a type of "plug-in" that would allow metacat to handle any new
actions without being recompiled.