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
Add instrumentation and tests for Grizzly 2.x Http Server #948
Conversation
f81f263
to
4b095a6
Compare
4b095a6
to
f5b7326
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the server test framework is really showing its value here. The similarity of the tests and instrumentations make it really easy to code review.
Some minor changes requested
|
||
@Override | ||
protected String[] instrumentationNames() { | ||
return new String[] {"jersey"}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jersey -> grizzly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
|
||
@Override | ||
protected String component() { | ||
return "jersey"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jersey -> grizzly
} | ||
|
||
@Path("/") | ||
static class ServiceResource { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's slightly confusing to have the same private class name in a class and superclass. Maybe ServiceResource
-> AsyncServiceResource
?
No description provided.