Skip to content
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

Avoid adding Objective constraints to second level or more in the resolution graph. #24

Open
debbabi opened this issue May 17, 2013 · 2 comments

Comments

@debbabi
Copy link
Contributor

debbabi commented May 17, 2013

Example:

When creating an instance that correspond to the "n" element specification, the resolver should create an instance of "comp1" component. In the current version, it should also verify that this newly created instance "hasSourceComponent" "comp2". This will never true.

Thus, we should avoid adding objective constraint as second level or more in the resolution graph.

@ghost ghost assigned debbabi May 17, 2013
@debbabi
Copy link
Contributor Author

debbabi commented May 17, 2013

Partially Fixed! we should outline all the possible cases.
Actual solution is just avoid testing binary objective constraints!

@debbabi debbabi closed this as completed May 17, 2013
debbabi added a commit that referenced this issue May 17, 2013
@debbabi
Copy link
Contributor Author

debbabi commented May 18, 2013

Problem in tutorial3

@debbabi debbabi reopened this May 18, 2013
@debbabi debbabi removed their assignment Dec 11, 2014
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

1 participant