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: | JavaSource shall not create DataObjects when searching for Documents | ||
---|---|---|---|
Product: | java | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Source | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | apireviews |
Priority: | P4 | Keywords: | API_REVIEW_FAST |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jaroslav Tulach
2008-08-22 13:34:15 UTC
V1: Why DataEditorSupport? Wouldn't it be better to have this new API 'Datasystems free'? I don't get it. What would the method do, other than create the DataObject and ask it for an EditorCookie? Data objects are permitted to load Document's in special ways, e.g. applying some conversions from the disk file. If the call to DataObject.find is currently too slow, I would suggest optimizing this directly. It is said that "some data loaders are not written correctly" but there is no explanation of what is incorrect and why it cannot be fixed without an API change. Re: V1. independent from DataSystems? Where we would put that API? To editor? There is the Document property StreamDescriptionProperty, maybe you could have a map from all StreamDescriptionProperty to Documents somewhere? Do you want to do it? After lively discussion with Jan I can only agree that I do not have any numbers to measure how much time this behaviour really consumes. No additional indication that this is a significant flaw. Probably no need to invent some futuristic API to solve this issue. |