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: | Renamed an operator; change not propagated into other operators use of operator name | ||
---|---|---|---|
Product: | soa | Reporter: | jlautz <jlautz> |
Component: | IEP editor | Assignee: | pvarghese <pvarghese> |
Status: | REOPENED --- | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: | After change from TupleBasedWindow0 to 2MinuteSlidingWindow |
Description
jlautz
2008-06-26 02:31:46 UTC
Created attachment 63474 [details]
After change from TupleBasedWindow0 to 2MinuteSlidingWindow
reassigning. Changing this to an enhancement, as this was never supported. This fix needs the following 1. Operator attributes definition needs to be backed by the TableModel support to generate value changed Events that has the old and new values, when an user changed the attributes. Today irrespective of modification or addition the table attribute entries are always removed and added and hence value change PropertyChange events are never generated. 2. Need to provide attribute (SchemaAttribute) references between connected operators to propagate changes from one operator attributes to the referenced operator. Today its maintained using string literals and this does not suffice for this functionality. As discussed will not be addressed for this release Reopened to be fixed in later release |