As I understand, component names are only use for saving information about components to XML configs. Right? If yes, then why component names but not just class names?
Class names sometimes change, but you may want to keep compatibility with existing settings. There's nothing wrong with returning getClass().getName(), but using an implementation-indepent name will save you (and your plugin's users) from subtle surprises when you refactor the class name ;)
Class names sometimes change, but you may want to keep compatibility with existing settings. There's nothing wrong with returning getClass().getName(), but using an implementation-indepent name will save you (and your plugin's users) from subtle surprises when you refactor the class name ;)
Sascha
Thanks.
Each component has 2 identifying parameters (interface-class and name). It seems to me one is enough :)