This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 197521 - component implementation - separating framework vs. extension code
Summary: component implementation - separating framework vs. extension code
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Joel Hawkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 196050
  Show dependency tree
 
Reported: 2007-07-23 14:14 EDT by Hubert Leung CLA
Modified: 2012-01-03 13:54 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hubert Leung CLA 2007-07-23 14:14:08 EDT
- Some methods in component implementations can be pushed to the framework.  For example, acceptWireTarget and addListener methods are framework code.  
- The ComponentEventSource interface can be implemented by the AbstractSource class.
- Each type of component has an abstract class.  For example, AbstractSource, AbstractFilter, AbstractTransform and Abstract Persistor.  The code of these abstract classes and their roles are very similar.  They implement the logic for finding the wire methods and handling the parameters by reflection, and implements a method to dispatch events to the consuming components.  I think most of these code belong to the context, so they don't need to be repeated in the super class for every component type.  We can treat the context as a controller that routes data through the assembly components as instructed by the assembly XML.
Comment 1 Joel Hawkins CLA 2008-04-30 22:13:15 EDT
The DC Assembly feature is deprecated.
Comment 2 Don Ebright CLA 2008-05-07 16:25:07 EDT
Bugzilla cleanup - closing this bug which won't be fixed.