This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Eager registration of DatabaseRuntimes | ||
---|---|---|---|
Product: | db | Reporter: | _ rkubacki <rkubacki> |
Component: | Code | Assignee: | Andrei Badea <abadea> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | apireviews, issues |
Priority: | P3 | Keywords: | API, PERFORMANCE |
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ rkubacki
2005-03-30 13:37:35 UTC
Radime, could you please elaborate on this? What is the flaw? Is it that the registration must be done by each module in a ModuleInstall.restored() method? What would be the right way to make this lazy? What about registering the DatabaseRuntimes in the default lookup and retrieving them only when they are needed (i.e., when a db connection is made)? Yes, the need for ModuleInstall.restored is bad. It is called even if the user has no intent to do anything related to DB. Registering through lookup is OK IMO. Fixed by the new Database Explorer API developer under issue #61439. VERIFIED |