- [jax-rs-spec users] [jsr339-experts] are we sticking with current itnerfaces?
- [jax-rs-spec users] [jsr339-experts] Default Servlet Mapping?
- [jax-rs-spec users] [jsr339-experts] Please review: simplified client bootstrapping API
- [jax-rs-spec users] [jsr339-experts] Response headers are writable without a builder
- [jax-rs-spec users] [jsr339-experts] Response.isEntityRetrievable() and Response.bufferEntity()
- [jax-rs-spec users] [jsr339-experts] Updated Schedule
- [jax-rs-spec users] [jsr339-experts] Updates to the JAX-RS async API
- [jax-rs-spec users] evaluate Preconditions in an independent class
- [jax-rs-spec users] Is the Form class mutable?
- [jax-rs-spec users] Mismatch with path parameter handling
- [jax-rs-spec users] Use "extensible enums" for HTTP codes, Mediatypes, Headers, Link Relation?
- 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?
- evaluate Preconditions in an independent class
- Injecting a sub-resource method path parameter into a resource field - legal or not?
- Is the Form class mutable?
- 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 @Path
- Updates to the JAX-RS async API
- Use "extensible enums" for HTTP codes, Mediatypes, Headers, Link Relation?
- Last message date: Fri Mar 30 02:25:16 2012
- Archived on: Thu Aug 10 15:12:26 2017 PDT