Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
AF3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 257
    • Issues 257
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • af3
  • AF3
  • Issues
  • #3896

Closed
Open
Opened Dec 10, 2019 by Alexander Diewald@diewaldGuest

Support directed connectors in the kernel

Current status

IConnectors that define an incoming or outgoing direction are currently created in AF3 plugins. This is recurring pattern and thus can be generalized. However, no generic code can be written for these IConnectors as of now.

Proposed change

  • Change the IConnector to implement a getOwner() method that wraps calls to the eContainer() field.
  • Add the interfaces IInputConnector and IOutputConnector that have the input and output reference lists as before. They shall inherit from the reduced IConnector interface.
  • Create an IInOutputConnector interface that unifies the IInputConnector and IOutputConnectors.
  • Migration of the “owner” field should not be needed since the EMF-encoded containment relations already duplicates the owner reference in the eContainer field.

(from redmine: issue id 3896, created on 2019-12-10)

  • Relations:
    • relates #3883 (closed)
    • blocks #3897
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: af3/af3#3896