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

ExposedServiceUrlAnalyzer update() evaluation for Conflicting Extensions does not work as intended #150

Open
christopher-johnson opened this issue Sep 12, 2017 · 0 comments

Comments

@christopher-johnson
Copy link

The code here tries to read e1 and e2 as uris when these are strings. The method also does not throw if it gets to the warning even though the test is expecting one. Instead it ends up comparing two nulls and returning an NPE.

I assume that ServiceExposingBinding match(..) will always need an update first, which does not happen with init.await(). When I replaced init.await() with this.update() and removed toTest.update() from the test setup, the only test that failed was conflictingExtensionsTest because the update() returns an NPE. If e1.uri and e2.uri are replaced with e1.toString() and e2.toString(), then the test still fails because of the fail "Should have thrown an exception upon update" expectation, that does not exist in the method.

I am not sure exactly why you introduce the Initializer interface for Runnable tasks, but this makes the whole thing rather difficult. How does this init method work? I do not get why you need to store the initializer interface in a private variable called init at all. Wouldn't it be clearer to use Runnable methods on instantiated tasks if you need to?

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

No branches or pull requests

1 participant