Hello,It is a good remark! I noticed it when worked on REST api doc generation [1].In my REST services I always use JSON or empty body and it looks like a pure api. text/plain is not compatible with it. Think, that it will be better to fix it in later releases.
Best regards,Idel Pivnitskiy--2015-04-29 18:50 GMT+03:00 Lukáš Fryč <lukas.fryc@gmail.com>:Hey guys,one issues Tadeas identified during testing sender endpoint via Java Sender lib is connected to this quiet change in the REST response from REST Sender endpoint (we added text/plain response specification):As we were always responding with "Job submitted", admin-ui client started to complain about the response not being JSON. So obvious fix was change that to text/plain, right?Not really.. some clients like Java Sender lib already expects application/json and JAX-RS then refuses these requests:The question is, what should be the correct response?There are many options, I would be perfectly fine with 204 No Content reply,but JSON might be more appropriate for future extensions, we may want to return e.g. PushMessageInformation#id or something else as part of the response.So, wouldn't be application/json more appropriate than text/plain? We may send empty body now {}.Is this something we want to address for Alpha? Or should we release fixed Java Sender lib?Cheers,~ Lukas______________________________________________________________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev