Response/ResponseBuilder should be Generic

[jakartaee]

Response/ResponseBuilder should be Generic

[glassfishrobot]

• Issue Imported From: https://github.com/jax-rs/api/issues/20
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[glassfishrobot]

@glassfishrobot Commented
Reported by [email protected]

[glassfishrobot]

@glassfishrobot Commented
sandoz said:
It's a bit of a hack but one can recast rather than wrap state.

public class Main {

   public static class Response<T> {

       private final T entity;

       private Response(T entity) {
           this.entity = entity;
       }

       public T getEntity() {
           return entity;
       }

       public static <T> ResponseBuilder<T> start() {
           return new ResponseBuilder<T>();
       }

       public static class ResponseBuilder<T> {
           private T entity;

           public ResponseBuilder<T> header(String name, String value) {
               return this;
           }

           public <V> ResponseBuilder<V> entity(V ent) {
               ResponseBuilder<V> vThis = (ResponseBuilder<V>)this;
               vThis.entity = ent;
               return vThis;
           }

           public Response<T> build() {
               return new Response<T>(entity);
           }
       }

       /**
        * @param args the command line arguments
        */
       public static void main(String[] args) {

           Response<String> stringResponse = Response.start()
   .entity(1)
   .entity("String")
   .header("Content-Type", "cheese")
   .build();
       }
   }
}

[glassfishrobot]

@glassfishrobot Commented
@mpotociar said:
Targeting for 2.0 PFD, but might need to be moved to 2.0 MR.

[glassfishrobot]

@glassfishrobot Commented
@mpotociar said:
Deferring to post-2.0 evaluation.

Since we would end up using type-erased Response in a lot of places, perhaps it would be better to consider introducing a generic response sub-class instead (like in Jersey 1.x).

[glassfishrobot]

@glassfishrobot Commented
c.beikov said:
What about custom Response beans similar to what resteasy offers with ResponseObjects(https://github.com/resteasy/Resteasy/blob/master/jaxrs/resteasy-jaxrs/src/test/java/org/jboss/resteasy/test/finegrain/client/ResponseObjectTest.java)??) That would also allow rich client APIs.

[glassfishrobot]

@glassfishrobot Commented
Issue-Links:
is duplicated by
JAX_RS_SPEC-108

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JAX_RS_SPEC-15