You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Various small code-cleaning TO-DOs, in decreasing priority:
change package and plug-in namespace, to cz.zcu.kiv.epf.spade
correct the path separator in ExportPatternSQLService::createSQLScript()
add comments at least for important and non-obvious classes, explain use of javax.xml.bind annotations in some domain classes
name ExportPatternData misleading, better rename to ExportPatternConfig ?
ExportPatternMapService::parseMainDescription() and parseMethodPluginDescription() should use a separate utility class/functoid for parsing attributes from description, for maintainability and extensibility
use logging consistently, e.g. in ExportPatternSQLService
given that ExportPatternSQLService is hard-wired into ExportPatternService::export(), extending the functional plug-in with other export methods is not that easy as it could be, e.g. if the given exporter was injected (into the IExportPatternSpecificService interface, currently not really used) based on UI option selection; thesis text mentions "xml_generating" branch which does not seem to exist
Various small code-cleaning TO-DOs, in decreasing priority:
Parent: #1