- *javascript*: I always doubt on it but it is more in term of feature than behavior - application/*x-json: doesn't do what you think (doesnt match application/foox-json or application/foo+x-json) - application/*+json: doable thanks to the "+" which is now well handled by CXF. Issue on johnzon side is we have to support more than tomee so maybe something we can just do on tomee side.
FYI https://issues.apache.org/jira/browse/TOMEE-1719 Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-02-25 17:19 GMT+01:00 ravi <[email protected]>: > Hi Romain, > > Do you see any problems if we configure the default providers Johnzon and > Jsr as below > > @Provider > @Produces({ > "application/json", > "application/*+json", "application/*x-json", > "application/javascript", "application/x-javascript" > }) > @Consumes({ > "application/json", > "application/*+json", "application/*x-json", > "application/javascript", "application/x-javascript" > }) > public class JohnzonProvider<T> extends DelegateProvider<T> { > } > > @Provider > @Produces({ > "application/json", > "application/*+json", "application/*x-json", > "application/javascript", "application/x-javascript" > }) > @Consumes({ > "application/json", > "application/*+json", "application/*x-json", > "application/javascript", "application/x-javascript" > }) > public class JsrProvider extends DelegateProvider<JsonStructure> { > public JsrProvider() { > super(new JsrMessageBodyReader(), new JsrMessageBodyWriter()); > } > } > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Tomee-7-0-0-M2-JaxRs-Client-No-message-body-reader-has-been-found-for-class-ContentType-application-n-tp4677664p4677682.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
