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: | All Property editors that access existing database tables should be consistent | ||
---|---|---|---|
Product: | soa | Reporter: | jlautz <jlautz> |
Component: | IEP editor | Assignee: | Ritesh Adval <radval> |
Status: | REOPENED --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
jlautz
2008-09-18 19:01:18 UTC
The ExternalTablePollingStream and ReplayStream are different from TableInput/TableOutput/SaveStream. In these two user has to select table as well as columns and that too of an existing table so the UI is provided for selecting table and existing columns. In case of TableInput, user adds attribute in the dialog and the table name (global id) can be a non existing table, or an existing table. Just for selecting an existing table it is not a good idea to have the select table ui. Same goes for TableOutput, the table name (global id) can be a non existing table. In case of SaveStream, when it has some input operator connected to it, it already has info regarding column names so just for table name selection we do not need to provide the UI. Here also Table can be an exisiting table or a new one will be created if one does not exists. Regarding title in ReplayStream, I have changed it to "Select Table which has Stream Events (ex: Table used in Save Stream )" I am marking this as fixed. This is the only thing which can be fixed. I would like to revisit this as a usability and aesthetic issue, so am reopening as an enhancement. In the cases where the user is likely to use an existing table (TableInput, for example), but won't specify attributes in a selection wizard, the ability to browse for existing table names and pick one is far more polished-feeling than having to go to other dialogs to figure it out, then come back. If the user is creating a new table, that can be handled by allowing the user to specify a name instead of browsing to select one (analagous to how file specifications are done). Again, I'll mention that the inconsistency among the table-related operators is confusing and feels accidental. |