- [jax-rs-spec users] [jsr339-experts] client filter issue
- [jax-rs-spec users] [jsr339-experts] Client initialization on server-side
- [jax-rs-spec users] [jsr339-experts] Consistency and awkwardness issues with Request/Response/Filter API
- [jax-rs-spec users] [jsr339-experts] EDR2 Published
- [jax-rs-spec users] [jsr339-experts] General rule for exposing/manipulating header values
- [jax-rs-spec users] [jsr339-experts] HEADS-UP: Please provide your feedback!
- [jax-rs-spec users] [jsr339-experts] Injecting a sub-resource method path parameter into a resource field - legal or not?
- [jax-rs-spec users] [jsr339-experts] Matching Algorithm in Spec
- [jax-rs-spec users] [jsr339-experts] PreMatchRequestFilter ambiguities and issues
- [jax-rs-spec users] [jsr339-experts] service locators and class-level @Path
- [jax-rs-spec users] [jsr339-experts] the weird states of Request on server side
- [jax-rs-spec users] [jsr339-experts] Updating requests/responses in Filters
- [jax-rs-spec users] [jsr339-experts] Why is Reader/WriterInterceptor generic?
- client filter issue
- Client initialization on server-side
- Concerns about the client-side exception hierarchy
- Consistency and awkwardness issues with Request/Response/Filter API
- General rule for exposing/manipulating header values
- HEADS-UP: Please provide your feedback!
- Injecting a sub-resource method path parameter into a resource field - legal or not?
- Matching Algorithm in Spec
- PreMatchRequestFilter ambiguities and issues
- Request interface duplicates MBRs, HttpHeaders and UriInfo
- service locators and class-level @Path
- Target Configuration initialization
- the weird states of Request on server side
- Updating requests/responses in Filters
- Why is Reader/WriterInterceptor generic?
- Last message date: Fri Feb 24 12:40:30 2012
- Archived on: Thu Aug 10 15:12:26 2017 PDT