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

Issues #5 and #107: Clarify integration with CDI and FT #140

Merged
merged 1 commit into from
Dec 12, 2018

Conversation

andymc12
Copy link
Contributor

@andymc12 andymc12 commented Dec 7, 2018

Includes new "Integration" section in the spec document and new TCK test cases for CDI interceptor support.

This should resolve issues #5 and #107.

Signed-off-by: Andy McCright j.andrew.mccright@gmail.com

@andymc12 andymc12 added this to the 1.2 milestone Dec 7, 2018
@andymc12 andymc12 self-assigned this Dec 7, 2018
[[integration]]
== Integration with other MicroProfile technologies

The MicroProfile Rest Client can be used as a standalone technology. That means that an implementation could work without CDI, MicroProfile Config, etc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't "The MP RC can be used as a standalone tech..." sound a bit like the implementations should work without Config and CDI?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I want to communicate that CDI and Config are not strictly necessary - as the user could use the RestClientBuilder to programmatically create the client instance, set the base URI/URL, register providers, etc.

=== Other MicroProfile Technologies

Client requests can be automatically traced when using MP OpenTracing. Likewise, requests can be measured using MP Metrics.
Configuration and usage of these technologies should be defined their respective specification documents.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing an "in" between defined and their?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Fixed.

Includes new "Integration" section in the spec document
and new TCK test cases for CDI interceptor support.

Signed-off-by: Andy McCright <j.andrew.mccright@gmail.com>
@andymc12
Copy link
Contributor Author

Thanks for the reviews Ken and Michal!

@andymc12 andymc12 merged commit 32a0abe into eclipse:master Dec 12, 2018
" http://java.sun.com/xml/ns/javaee" +
" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">" +
" <interceptors>" +
" <class>org.eclipse.microprofile.rest.client.tck.interfaces.LoggableInterceptor</class>" +
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is CDI 1.0 style (i.e. very old) of enabling an interceptor. I'd prefer using @Priority annotation (see also the Interceptors spec, 5.1 Defining Interceptor Order) - the test would be simpler and easier to understand.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mkouba - I think that makes sense. Since this has already been merged, would you mind opening a new PR with your proposed changes?

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

Successfully merging this pull request may close these issues.

4 participants