From: Kieran K. (JIRA) <jir...@ob...> - 2009-06-24 16:23:44
|
plugin not identified by ERXModel if defined in jdbc URL instead of plugin key of connection dictionary (patch attached) ------------------------------------------------------------------------------------------------------------------------ Key: WONDER-320 URL: http://issues.objectstyle.org/jira/browse/WONDER-320 Project: Project Wonder Issue Type: Bug Environment: Wonder #9515 Reporter: Kieran Kelleher If plugin key of connection dictionary returns null, we now fallback to using ERXEOAccessUtilities.guessPluginName(model) (FYI, used by ERXModelGroup for same connection dictionary scenario) to get the plugin name from the connection URL. debug logging added to show the full list of prototype entity names (some are derived from combinations of adaptor name, model name and plugin name) that are searched for prototype attributes. javadoc added to explain the naming conventions and override priority of prototype entities provided by extended prototype feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |