Skip to content

Flow through data component cannot be instantiated #643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lwrage opened this issue Oct 28, 2015 · 4 comments
Closed

Flow through data component cannot be instantiated #643

lwrage opened this issue Oct 28, 2015 · 4 comments

Comments

@lwrage
Copy link
Contributor

lwrage commented Oct 28, 2015

The end to end flow in the following model is not instantiated.

package issue643
public
    system top

    end top;

    system implementation top.i
        subcomponents
            p: system S;
            c: system S;
            d: data;
        connections
            c0: data access p.a <-> d;
            c1: data access d <-> c.a;
        flows
            e2e: end to end flow p -> c0 -> d -> c1 -> c;
    end top.i;

    system S
        features
            a: requires data access;
    end S;

end issue643;

@lwrage
Copy link
Contributor Author

lwrage commented Nov 3, 2015

Fixing #246 will likely help. In general, the flow instantiation must be changed to work for bidirectional connection instances.

@lwrage lwrage self-assigned this Nov 3, 2015
@lwrage lwrage added the backlog label Jan 9, 2018
@lwrage
Copy link
Contributor Author

lwrage commented Jan 11, 2018

It is not clear if we should even have bidirectional connection instance.

@AaronGreenhouse
Copy link
Contributor

Fixed by Issue #676

@AaronGreenhouse
Copy link
Contributor

Added JUnit tests for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants