- [jax-rs-spec users] Consistency and awkwardness issues with Request/Response/Filter API
- [jax-rs-spec users] Response headers are writable without a builder
- [jsr339-experts] are we sticking with current itnerfaces?
- [jsr339-experts] Default Servlet Mapping?
- [jsr339-experts] Please review: simplified client bootstrapping API
- [jsr339-experts] Response headers are writable without a builder
- [jsr339-experts] Response.isEntityRetrievable() and Response.bufferEntity()
- [jsr339-experts] Updated Schedule
- [jsr339-experts] Updates to the JAX-RS async API
- are we sticking with current itnerfaces?
- Concerns about the client-side exception hierarchy
- Consistency and awkwardness issues with Request/Response/Filter API
- Default Servlet Mapping?
- Injecting a sub-resource method path parameter into a resource field - legal or not?
- Matching Algorithm in Spec
- Please review: simplified client bootstrapping API
- Response headers are writable without a builder
- Response.isEntityRetrievable() and Response.bufferEntity()
- service locators and class-level _at_Path
- Updates to the JAX-RS async API
- Last message date: Fri Mar 30 08:41:49 2012
- Archived on: Thu Aug 10 15:12:00 2017 PDT