Move Attributes to RestEase.Annotations
See original GitHub issueI guess it would be nice if all attributes were moved to separate package, let’s say RestEase.Annotations
so interface won’t have dependency on specific version of RestEase
(RestEase.Annotations
should not change that often).
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Looking forwards to RestEase 2 · Issue #150
I want to move all common types (attributes, RequestInfo , Requester , etc) to a RestEase.Core assembly. This is necessary to let source ......
Read more >Writing REST Services with RESTEasy Reactive
Any class annotated with a @Path annotation can have its methods exposed as REST endpoints, provided they have an HTTP method annotation (see ......
Read more >RESTEasy JAX-RS - JBoss.org
This client-side framework allows you to map outgoing HTTP requests to remote servers using JAX-RS annotations and interface proxies. JAX-RS implementation ...
Read more >RESTEasy Client API
A quick guide to building out a client for the REST API using RESTEasy.
Read more >RESTEasy Reference Guide JBoss Enterprise Application ...
The @Path annotation has an attribute called encode. This controls whether the literal part of the value supplied (that is, the characters that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is this actually a scenario you face?
If not, let’s hold off until Amazon start releasing their apis as RestEase interfaces… I don’t think that’s a good usage of RestEase anyway: I think if the interfaces as implementation details of the comms layer, rather than as things which are exposed, in any semi-complex application anyway.
On 11 June 2017 19:41:16 BST, Milosz Krajewski notifications@github.com wrote:
Closing as no response.